Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Allow wildcard specification for ignoreChanges #6710

Open
jen20 opened this issue Apr 6, 2021 · 0 comments
Open

Allow wildcard specification for ignoreChanges #6710

jen20 opened this issue Apr 6, 2021 · 0 comments
Labels
area/engine Pulumi engine customer/feedback Feedback from customers kind/enhancement Improvements or new features

Comments

@jen20
Copy link
Contributor

jen20 commented Apr 6, 2021

Currently, each field for which changes should be ignored on a resource must be listed. There are some times however when it is really useful in a pinch to prevent any changes to a given resource even though that means drift between program and state.

This is currently achievable by listing every top-level field in the resource in ignoreChanges, but it would be more usable and provider-upgrade-proof to be able to specify a wildcard instead.
@jen20 jen20 added the kind/enhancement Improvements or new features label Apr 6, 2021
@mikhailshilkov mikhailshilkov added kind/enhancement Improvements or new features and removed kind/enhancement Improvements or new features labels Apr 6, 2021
@mikhailshilkov mikhailshilkov added the area/engine Pulumi engine label Jul 28, 2022
@mnlumi mnlumi added the customer/feedback Feedback from customers label Oct 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/engine Pulumi engine customer/feedback Feedback from customers kind/enhancement Improvements or new features
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jen20 @mikhailshilkov @mnlumi