-
Notifications
You must be signed in to change notification settings - Fork 113
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
Elide last applied configuration annotation when SSA is supported #1863
Conversation
Does the PR have any schema changes?Looking good! No breaking changes found. |
Does the PR have any schema changes?Looking good! No breaking changes found. |
3 similar comments
Does the PR have any schema changes?Looking good! No breaking changes found. |
Does the PR have any schema changes?Looking good! No breaking changes found. |
Does the PR have any schema changes?Looking good! No breaking changes found. |
a9e039a
to
87b009f
Compare
Does the PR have any schema changes?Looking good! No breaking changes found. |
…rted (pulumi#1863)" This reverts commit 11e356e.
…rted (pulumi#1863)" This reverts commit 11e356e.
…rted (pulumi#1863)" This reverts commit 11e356e.
Proposed changes
When server side applies are supported, storing last applied configuration seems redundant. We have longstanding plans of toggling server side apply support to be on by default - see #1556. This change elides last applied config annotation when server-side apply support is enabled. This seems safe since SSA support is not enabled by default anyway thus reducing any potential risk of unexpected behavior change with this.
Related issues (optional)
Fixes #1048