Allow use with terraform v0.12.x and add metadata options for aws_launch_config #182
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
i will tag this release |
rhysemmas
approved these changes
Aug 24, 2020
Yeh makes sense, i'll tag with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit will allow terrafying-components to be compatible with terraform v0.12.x.
If you're still using terraform v0.11.x please use an older version of terrafying-components.
bundle exec terrafying json xxx.rb > xxx.tf.jsonis required when using terraform v0.12.xChanges:
Added metadata_option for aws_launch_configuration. (currently requires custom aws provider)
Added additional keys required for security_groups.
Changed the use of hexdigest to bubblebabble for aws_lb. (terraform v0.12.0 A name must start with a letter or underscore)