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

Ensure that base64 lookup codec encodes the bytes object as a string #742

Merged

Conversation

acmcelwee
Copy link
Member

@acmcelwee acmcelwee commented Aug 6, 2019

We recently updated our python runtime for stacker from 2 to 3, and using the file lookup with the base64 codec results in the output being a bytes object (b'foo...'), instead of a string that's usable as a CFN parameter or even a local stacker variable.

Fixes #693.

@russellballestrini
Copy link
Member

@acmcelwee
Copy link
Member Author

@russellballestrini, thanks for the read. I added a changelog entry (with a force push to keep the commit history clean). I'll let you give it a final look before I merge it, or also feel free to merge it yourself, if it looks good to you.

@russellballestrini
Copy link
Member

Looks good to me! Merge away!

@russellballestrini russellballestrini merged commit 8278add into cloudtools:master Aug 15, 2019
@acmcelwee acmcelwee deleted the base64-lookup-decode branch August 15, 2019 16:23
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

Successfully merging this pull request may close these issues.

base64 lookup contents are repr'd as byte strings causing AWS to reject it
2 participants