Skip to content

Fix two lifecycle rules with different no_age value always generates change issue#7060

Merged
modular-magician merged 1 commit into
hashicorp:mainfrom
modular-magician:downstream-pr-12b3ce1062029cd144b66e51d511c12532df9363
Mar 7, 2024
Merged

Fix two lifecycle rules with different no_age value always generates change issue#7060
modular-magician merged 1 commit into
hashicorp:mainfrom
modular-magician:downstream-pr-12b3ce1062029cd144b66e51d511c12532df9363

Conversation

@modular-magician
Copy link
Copy Markdown
Collaborator

Fixes hashicorp/terraform-provider-google/issues/17314

storage: fixed two or more lifecycle rules with different values of `no_age` field always generates change in `google_storage_bucket` resource.

Derived from GoogleCloudPlatform/magic-modules#10137

…s change. (hashicorp#10137)

[upstream:12b3ce1062029cd144b66e51d511c12532df9363]

Signed-off-by: Modular Magician <magic-modules@google.com>
@modular-magician modular-magician merged commit 46619b4 into hashicorp:main Mar 7, 2024
@modular-magician modular-magician deleted the downstream-pr-12b3ce1062029cd144b66e51d511c12532df9363 branch November 16, 2024 02:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

google_storage_bucket with two lifecycle rules with different values for no_age always reports change

1 participant