-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
[#4794] Don't Base64-encode EC2 userdata if it is already Base64 encoded #6140
[#4794] Don't Base64-encode EC2 userdata if it is already Base64 encoded #6140
Conversation
The user data may be Base64 encoded already - for example, if it has been generated by a template_cloudinit_config resource.
Looks good, thanks! Could I trouble you to throw some already encoded data into the config of the TestAccAWSInstance_vpc? You can reuse this user_data encoding. That will give us an acceptance test that verifies this works. Let me know! |
Hey @catsby, something like this? It doesn't decode to anything meaningful, but it passes as a valid Base64 encoding. |
40ff572
to
f020ebb
Compare
f020ebb
to
0181b6b
Compare
Yep! I'll to add the |
…se64 encoded (hashicorp#6140) * Don't Base64-encode EC2 userdata if it is already Base64 encoded The user data may be Base64 encoded already - for example, if it has been generated by a template_cloudinit_config resource. * Add encoded user_data to aws_instance acceptance test
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
The user data may be Base64 encoded already - for example, if it has been generated by a template_cloudinit_config resource.
Partially resolves #4794