-
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
Enable Server-Side Apply mode by default #2206
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the comment in provider.go starting L2138 need to be updated, now the default is server-side apply? It says
In the next major release, we will default to using Server-side Apply, which will simplify this logic.
We plan to drop the provider flag in |
Does the PR have any schema changes?Looking good! No breaking changes found. |
c14a841
to
beb5160
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This test was accessing an Output property without using an apply, and the value had not resolved already. Apparently this was working with the legacy Client-Side Apply implementation, but the test code was unsafe.
This comment was marked as outdated.
This comment was marked as outdated.
With Server-side Apply previews, updating an immutable field in a resource will result in a 422 error code from the API server. In these cases, Pulumi will replace the resource, so we need to ignore the error rather than failing the preview.
This comment was marked as outdated.
This comment was marked as outdated.
1 similar comment
Does the PR have any schema changes?Looking good! No breaking changes found. |
Hi @lblackstone
what should be the proper approach to solve the issue and become using the SSA? Best regards Petr context:AKS cluster version 1.23.8 (running since 2021-03-05) the kubernetes resource has following definition:
|
Same here 👍 we are getting this with cert-manager deployment:
|
This reverts commit 5960e58. # Conflicts: # CHANGELOG.md
@pstovik @dotansimha Sorry about that folks. SSA being on by default was reverted in v3.22.1, until we can clear up problems like those you reported. Bumping the package version will get the new provider (e.g., |
Proposed changes
Related issues (optional)