Repository navigation
KMS lookups give values $VAL wrapped as "b'$VAL'" when using python 3 #755
Description
Activity
- changed the title
[-]KMS lookups do not work if password is not valid base64[/-][+]KMS lookups give values $VAL wrapped as "b'$VAL'"[/+]on Mar 31, 2020 - changed the title
[-]KMS lookups give values $VAL wrapped as "b'$VAL'"[/-][+]KMS lookups give values $VAL wrapped as "b'$VAL'" when using python 3[/+]on Mar 31, 2020 after uninstalling via pip3 and reinstalling via pip2, the issue only affects Python 3. For what it's worth,
aws --versiongives meaws-cli/2.0.0 Python/3.7.3 Linux/4.4.0-17763-Microsoft botocore/2.0.0dev4This 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.1I went ahead and opened a pull request: #762
you're right, I hadn't cleaned out my python2 installation and am seeing this issue again
Hi guys,
Any chance to fix this in the next release? All the secrets are now showing as b'secret'
Thanks
I'll go ahead and get a dot release out by this weekend.
Reacted by matt bearyhttps://github.com/cloudtools/stacker/releases/tag/1.7.2 - released, sorry for the delay!
While attempting to encrypt a password 'hello!' per the directions here:
using the suggested encryption command
aws kms encrypt --key-id alias/DbConnectionKey --plaintext 'hello!' --output text --query CiphertextBlobresults in:From there, I attempted to use
aws kms encrypt --key-id alias/DbConnectionKey --plaintext fileb://<(echo -n 'hello!') --output text --query CiphertextBloband 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".