You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please list the steps required to reproduce the issue, for example:
terraform apply
Important Factoids
We use a lot of aws_volume_attachment declarations.
References
None.
Workaround
It appears possible to fix/improve this by adding:
lifecycle {
# Don't allow Terraform to update volume tags, because if it does, it will# erase tags on volumes attached by aws_volume_attachment.ignore_changes=["volume_tags"]
}
...to each affected instance.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 13, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
Terraform v0.9.4
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Debug Output
We can supply this if this proves difficult to reproduce, but we'll need to strip out proprietary data.
Panic Output
None.
Expected Behavior
Terraform should leave the
Name
of the volume alone, and not try to remove it.Actual Behavior
The plan always includes:
If run, this will strip the
Name
off our volume.Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
Important Factoids
We use a lot of
aws_volume_attachment
declarations.References
None.
Workaround
It appears possible to fix/improve this by adding:
...to each affected instance.
The text was updated successfully, but these errors were encountered: