Move volume_tags into dynamic blocks's tags parameter #197
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.
Description
This effectively removes the churning that is happening when an
ebs_volume is attached separately from the module
Takes advantage of the new feature in the aws provider available as of 3.24.0.
hashicorp/terraform-provider-aws#15474
Motivation and Context
When using this module and creating aws_ebs_volumes/aws_ebs_volume_attachments outside of the module causes constant apply churn because the tags conflict.
Breaking Changes
Tags on the ebs_block_volumes may change
Requires 3.24.0 of aws provider, since this is a major version requirement change in the module
How Has This Been Tested?
I took existing instances with externally defined ebs_volumes and upgraded to this module. I also created resources anew.
Note: I'm still doing a bit more testing to validate, I did notice some initial churn (had to apply twice). But even this is a major behavior improvement.