Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Conversation

modular-magician
Copy link
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. (#10137)

[upstream:12b3ce1062029cd144b66e51d511c12532df9363]

Signed-off-by: Modular Magician <[email protected]>
@modular-magician modular-magician requested a review from a team as a code owner March 7, 2024 18:03
@modular-magician modular-magician requested review from ScottSuarez and removed request for a team March 7, 2024 18:03
Copy link

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

@modular-magician modular-magician merged commit e62ca9f into GoogleCloudPlatform:main Mar 7, 2024
4 of 5 checks passed
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