Fix google_ces_guardrail persistent diff for llm_prompt_security#1341
Merged
Conversation
…780) [upstream:382f767609f031134a3ea07b74abaea6392833ad] Signed-off-by: Modular Magician <magic-modules@google.com>
modular-magician
merged commit a7c872b
into
terraform-google-modules:master
3 checks passed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add send_empty_value: true and allow_empty_object: true to defaultSettings property in Guardrail.yaml config to force sending the empty block to the API.
Without send_empty_value, terraform plan won't detect the empty value and keep trying to apply empty value to guardrail even if there's no change
Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.
Derived from GoogleCloudPlatform/magic-modules#17780