-
Notifications
You must be signed in to change notification settings - Fork 428
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
fix(manifest): escape env var values while rendering CFN template #1322
Conversation
Added the "do-not-merge" label while running e2e tests. |
I kind of miss our golden file integ tests. They'd compare the packaged cf template to the expected cf template. That'd help with this class of error. |
I'll use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
…s#1322) Use the %q verb (a double-quoted string safely escaped with Go syntax) when writing env var values. This ensures that values like `"{}"` or `on` are written as strings instead of a mapping or boolean object. Fixes aws#1120, fixes aws#1292 _By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice._
Use the %q verb (a double-quoted string safely escaped with Go syntax)
when writing env var values. This ensures that values like
"{}"
oron
are written as strings instead of a mapping or boolean object.Fixes #1120, fixes #1292
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.