You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, the CLI shell-escapes the variables it outputs (this might change in the future, as it can indeed be non-ideal in some cases, but for now that's the behavior).
Now, although I'm inclined to agree it's aesthetically unpleasing; technically, this formatting is a correct representation of your input:
sh-3.2$ TEST=a'
> 'a
sh-3.2$ printf "$TEST"
a
a
Is this a problem for you? If so, can you please clarify how? More information on your use case might at the very least help us in deciding whether shell-escaping is indeed the right thing to do.
This bug caused a config problem for us until we figured it out. One of our env vars has an @ character which displays escaped when you run aptible config. We were setting up a new stack and copied the output of that command which in turn wrote the wrong data on the new env var on the new stack.
I set a config variable TEST to
a\na
(and confirmed that this worked), but the CLI prints:The text was updated successfully, but these errors were encountered: