go: allow unknowns during update #15942
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently we reject all unknowns during `pulumi up`. However we are soon going to allow them to come through via `up --continue-on-error`, and thus should no longer error out when we have them.
Changelog[uncommitted] (2024-04-15)Features
|
Frassle
approved these changes
Apr 15, 2024
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently we reject all unknowns during
pulumi up. However we are soon going to allow them to come through viaup --continue-on-error, and thus should no longer error out when we have them.This is a similar preparatory PR to #15898, except that Go deals with the unknowns a little different, so we don't need to treat apply specially, but the marshalling.