Use create_before_destroy for launch_configuration #5
Conversation
This file contains hidden or 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
Motivation ---------- If the launch configuration changes, for example if the user data is modified, the new launch configuration must be created and applied to the auto scaling group before the old one may be destroyed. Modifications ------------- Use "name_prefix" instead of "name" for the launch configuration. Set lifecycle of "create_before_destroy" to true. Results ------- User data can be modified and applied to the existing auto scaling group without errors. The launch configuration will gain a random suffix, to avoid name conflicts.
|
I added in during small redesign, please take a look at 2.0.0 version. |
rraub
pushed a commit
to rraub/terraform-aws-rabbitmq
that referenced
this pull request
Nov 14, 2019
adding monitor tag to rabbit instances
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.
Motivation
If the launch configuration changes, for example if the user data is modified, the new launch configuration must be created and applied to the auto scaling group before the old one may be destroyed.
Modifications
Use "name_prefix" instead of "name" for the launch configuration.
Set lifecycle of "create_before_destroy" to true.
Results
User data can be modified and applied to the existing auto scaling group without errors.
The launch configuration will gain a random suffix, to avoid name conflicts.