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.

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

Make PULUMI_FORCE_NEW_FROM_SUBTYPES the default #3006

Closed
thomas11 opened this issue Jan 10, 2024 · 2 comments · Fixed by #3771
Closed

Make PULUMI_FORCE_NEW_FROM_SUBTYPES the default #3006

thomas11 opened this issue Jan 10, 2024 · 2 comments · Fixed by #3771
Assignees
Labels
3.0 kind/enhancement Improvements or new features resolution/fixed This issue was fixed

Comments

@thomas11
Copy link
Contributor

#2970 extended the setting of forceNew, which causes resources to be replaced on certain property changes, to sub-properties. Since this is potentially disruptive, the new behavior is gated behind an environment variable PULUMI_FORCE_NEW_FROM_SUBTYPES.

In v3, this should be default as it's more correct behavior, and we can call it out in the change notes.

@cleverguy25
Copy link

Added to epic https://github.com/pulumi/home/issues/3552

@EronWright EronWright self-assigned this Dec 6, 2024
@danielrbradley
Copy link
Member

To clarify, we should keep the environment variable, but allow it to be turned off instead of on in case users experience issues with it during their migration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.0 kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

5 participants