Skip to content

feat: base64 encoded user_data #107

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Jun 10, 2020
Merged

feat: base64 encoded user_data #107

merged 1 commit into from
Jun 10, 2020

Conversation

bryantbiggs
Copy link
Member

Description

Motivation and Context

closes #57

Breaking Changes

How Has This Been Tested?

- Add ability to use either string user_data or base64 encoded user_data similar to terraform-aws-modules/terraform-aws-ec2-instance#137
@antonbabenko antonbabenko merged commit f782612 into terraform-aws-modules:master Jun 10, 2020
@antonbabenko
Copy link
Member

v2.14.0 has been just released.

Closes #57

@bryantbiggs bryantbiggs deleted the feature/userdata branch June 10, 2020 16:51
@github-actions
Copy link

I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 29, 2022
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should change user_data to user_data_base64 to avoid string limit
2 participants