provider/aws: add name_prefix option to launch config #3802
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.
Fixes Issue #2911.
This adds a
name_prefix
option toaws_launch_configuration
resources, making thecreate_before_destroy
lifecycle pattern a bit more understandable in large configs.When specified,
name_prefix
is used instead of "terraform-" as the prefix for the launch configuration name, with the 26-character uuid appended. It's set to Conflict withname
, so existing functionality is unchanged.name
still sets the name explicitly.Added an acceptance test, and updated the site documentation.
Let me know if there's anything out of place or that you'd like to change.
Thanks!