-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
data-source/aws_instance: Add get_user_data argument and user_data_base64 attribute #8001
Conversation
…se64 attribute Reference: #5927 As contents may be large and not necessarily safe for the Terraform state, which requires valid UTF-8, we allow retrieving the Base64 contents of EC2 Instance user data into the `user_data_base64` attribute when a new `get_user_data` argument is set to `true`. Output from acceptance testing: ``` --- PASS: TestAccAWSInstanceDataSource_basic (149.59s) --- PASS: TestAccAWSInstanceDataSource_GetUserData (158.67s) ```
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.
I left one question around an additional test case for the basic configuration, but this is otherwise good to go.
…for instance without user data ``` --- PASS: TestAccAWSInstanceDataSource_GetUserData_NoUserData (210.42s) ```
This has been released in version 2.3.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Closes #5927
As contents may be large and not necessarily safe for the Terraform state, which requires valid UTF-8, we allow retrieving the Base64 contents of EC2 Instance user data into the
user_data_base64
attribute when a newget_user_data
argument is set totrue
. The SHA-1 hash of the EC2 Instance user data will continue to be set in theuser_data
attribute regardless of theget_user_data
argument.Output from acceptance testing: