Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Lines In Config Printed with ' #191

Open
cancan101 opened this issue Aug 24, 2016 · 2 comments
Open

New Lines In Config Printed with ' #191

cancan101 opened this issue Aug 24, 2016 · 2 comments

Comments

@cancan101
Copy link

I set a config variable TEST to a\na (and confirmed that this worked), but the CLI prints:

TEST=a'
'a
@krallin
Copy link
Contributor

krallin commented Aug 29, 2016

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.

Thanks!

@lacostenycoder
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants