Skip to content

[schema] Add replaceOnChanges option to resource properties #7798

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

Closed
lblackstone opened this issue Aug 19, 2021 · 0 comments · Fixed by #7874
Closed

[schema] Add replaceOnChanges option to resource properties #7798

lblackstone opened this issue Aug 19, 2021 · 0 comments · Fixed by #7874
Assignees
Labels
good-first-issue Start here if you'd like to start contributing to Pulumi kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Milestone

Comments

@lblackstone
Copy link
Member

#7226 added the replaceOnChanges option, which allows users to specify properties that will cause a resource replacement if they change.

This feature would be useful in generated SDKs to allow overrideable default replacement behavior. Here's a concrete example: pulumi/pulumi-kubernetes#1568 (comment)

Although replaceOnChanges is a resource option, it would probably be most useful to set at the property level, and then compute the resource-level list during code generation.

Affected feature

pulumi schema + replaceOnChanges resource option

@lblackstone lblackstone added the kind/enhancement Improvements or new features label Aug 19, 2021
@justinvp justinvp added the good-first-issue Start here if you'd like to start contributing to Pulumi label Aug 19, 2021
@iwahbe iwahbe self-assigned this Aug 24, 2021
@emiliza emiliza added this to the 0.61 milestone Aug 30, 2021
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Sep 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good-first-issue Start here if you'd like to start contributing to Pulumi kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants