-
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
core: Address some issues with ignore_changes #5635
Conversation
52aca02
to
c39bfd1
Compare
c39bfd1
to
4cd96ec
Compare
Awesome! Looking forward to this. |
Noting here that this is insufficient to fix the required attr case - since |
4cd96ec
to
97c0901
Compare
73fcfff
to
1dda0fe
Compare
The ignore_changes diff filter was stripping out attributes on Create but the diff was still making it down to the provider, so Create would end up missing attributes, causing a full failure if any required attributes were being ignored. In addition, any changes that required a replacement of the resource were causing problems with `ignore_chages`, which didn't properly filter out the replacement when the triggering attributes were filtered out. Refs #5627
1dda0fe
to
f480ae3
Compare
This LGTM, but we may want to revisit in future - definitely better than what we have now though! |
Discussed with @jen20 - while I'm not sure if this addresses all ignore_changes issues, it does definitely address some of them - enough to warrant including it and moving forward from there. |
core: Address some issues with ignore_changes
fixes my current ignore_changes issues; 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. |
The ignore_changes diff filter was stripping out attributes on Create
but the diff was still making it down to the provider, so Create would
end up missing attributes, causing a full failure if any required
attributes were being ignored.
In addition, any changes that required a replacement of the resource
were causing problems with
ignore_chages
, which didn't properly filterout the replacement when the triggering attributes were filtered out.
Refs #5627