Set a default value for envs in Cloud Run Job #9681
Merged
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.
What?
google_cloud_run_v2_job
resource.Why?
env
set, theenv
set is re-ordered which results in a large diff, see Cloud Run env variables reordering causing resource to update in-place terraform-provider-google#7467 for an example. The cause for this seems to be that in the Terraform state the envvalue
is""
when using avalue_source
(i.e. a reference to agoogle_secret_manager_secret
), but in the plan the value isnil
(as it has not been set), which then triggers all of the envs to have changed.Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.
Derived from GoogleCloudPlatform/magic-modules#13487