Fix bug that prevented setting 'create_ignore_already_exists' on existing resources #7236
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
…ting resources (#10394) [upstream:a841407f5886c4a0009c0fe62391c45e962529a0] Signed-off-by: Modular Magician <[email protected]>
modular-magician
deleted the
downstream-pr-a841407f5886c4a0009c0fe62391c45e962529a0
branch
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 if
create_ignore_already_existsis the only field updated on a resource, the update will fail with "Error 400: Invalid field mask for ServiceAccount". Since this flag only controls Terraform behavior it should not trigger an update to the service account.Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#10394