KMS lookups give values $VAL wrapped as "b'$VAL'" when using python 3

[hauntingEcho]

While attempting to encrypt a password 'hello!' per the directions here:

1. the command given for encryption fails entirely
2. after getting encryption working, Stacker populated incorrect values

using the suggested encryption command aws kms encrypt --key-id alias/DbConnectionKey --plaintext 'hello!' --output text --query CiphertextBlob results in:

Invalid base64: "hello!"

From there, I attempted to use aws kms encrypt --key-id alias/DbConnectionKey --plaintext fileb://<(echo -n 'hello!') --output text --query CiphertextBlob and used the result to create a secret via Stacker. In this secret, I see:

Does this need a different configuration than the one from the docs, or is there another way I should be doing this? I'm currently using Stacker 1.7.0 on python 3.5.3. I've also tried dropping the '!' off the end and received the same behavior with just "hello".

[hauntingEcho]

after uninstalling via pip3 and reinstalling via pip2, the issue only affects Python 3. For what it's worth, aws --version gives me aws-cli/2.0.0 Python/3.7.3 Linux/4.4.0-17763-Microsoft botocore/2.0.0dev4

[hauntingEcho]

This has been resolved with 1.7.1

[baryal1299]

This has been resolved with 1.7.1

Still seeing the same issue, is this fixed for python 3?

$ aws --version aws-cli/1.16.199 Python/3.6.7 Darwin/18.7.0 botocore/1.15.39 $ stacker --version stacker 1.7.1

I went ahead and opened a pull request: https://github.com/cloudtools/stacker/pull/762

[hauntingEcho]

you're right, I hadn't cleaned out my python2 installation and am seeing this issue again

[bmcoelho]

Hi guys,

Any chance to fix this in the next release? All the secrets are now showing as b'secret'

Thanks

[hauntingEcho]

It looks like this should be fixed by your PR #765 , pending release ( #766 )

[phobologic]

I'll go ahead and get a dot release out by this weekend.

[phobologic]

https://github.com/cloudtools/stacker/releases/tag/1.7.2 - released, sorry for the delay!