We recently had to restore an EBS volume to an EC2 instances that had been deployed in terraform. This now means subsequent terraform plan/apply highlights that the instance in question will be destroyed and recreated - we don't want to do this.
We can workaround this at present in one of two ways, however these aren't appropriate in all the environments we manage and therefore I'd like to request an approach that would scale better in ours (and hopefully others') use cases.
e.g. terraform wouldn't care about the changing snapshot id but would care if volume_size or delete_on_termination changed.
Is this remotely possible?
Sorry if this is similar to requests you've had before - I did search through existing bugs & feature requests and while I saw a few talking about behaviour of ignore_changes - i couldn't see anything that matched the above scenario.
The text was updated successfully, but these errors were encountered:
Thanks for filing the issue.
We have a few versions of this open already, like #6632 and #5666, so I'm going to close this in preference to the existing issues.
However, even with a proposed change to allow some sort of attribute addressing within ignore_changes, that won't directly apply to ebs_block_device attribute, because those are a set type which is not addressable. While there's some relevant discussion over in #9693, it's really going to rely on the provider changing the resource itself to allow for addressing of that particular attribute.