-
Notifications
You must be signed in to change notification settings - Fork 9.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ignore_changes lifecycle policies preventing initialization of a resource element #5280
Comments
I'm having this same issue. Here is some code to reproduce this problem. The code itself:
Running the
But when trying to run
|
Also related to this is another scenario that isn't working as expected with I've created a server using the same bug.tf that I showed previously but with the
Immediately after creation, I ran
Then I put back in the
I ran
Please let me know if you need any additional information for reproducing this issue. Thanks, |
Hi guys, Thanks for the info and sorry to see you're running into this. I'll take a look as soon as I can and see if I can pinpoint the problem. Thanks, |
Thanks @jtopjian! Let me know if you need anything. |
I re-read this issue and missed the first message that included |
Hi folks, I'm working on |
Thanks! |
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. |
Hi,
When I set a lifecycle policy to
ignore_changes
, it won't let me apply an initial value to the targeted parameter. Is this the expected behavior?For example, let's say I assign this policy to an aws_network_interface:
lifecycle { "ignore_changes" = ["private_ips"] }
And I also configure this as part of the resource:
private_ip = "10.1.1.1"
Then when I apply for the first time, Terraform (current master version) will ignore the 10.1.1.1 private_ip I configured. I was expecting it to ignore changes that arise after creation, but not to ignore my initial configuration.
The text was updated successfully, but these errors were encountered: