-
Notifications
You must be signed in to change notification settings - Fork 286
fix(storage): fix the lifecycle storage sample #865
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(storage): fix the lifecycle storage sample #865
Conversation
|
Hi @gurusai-voleti. To help us understand the context of this change, can you please update the PR description to include a reference to a bug with the rationale for the change. This will help us understand the intent of this PR. Thanks in advance! |
@glasnt updated the description please check, there is only internal bug on buganizer for this issue |
|
/gcbrun |
Co-authored-by: Katie McLaughlin <[email protected]>
|
/gcbrun |
|
/gcbrun |
…les#865) * fix(storage): fix the lifecycle storage sample * Update storage/object_lifecycle_setting/main.tf Co-authored-by: Katie McLaughlin <[email protected]> * Revert "Update storage/object_lifecycle_setting/main.tf" This reverts commit a1ee4eb. * fix(storage): fix the lifecycle storage sample * lintttt --------- Co-authored-by: Katie McLaughlin <[email protected]> Co-authored-by: Katie McLaughlin <[email protected]>
Description
in object life cycle example uniform_bucket_level_access is not needed and it might be misleading for the customers, so refined the example to remove the uniform_bucket_level_access flag
Fixes #
Note: If you are not associated with Google, open an issue for discussion before submitting a pull request.
Checklist
Readiness
Style
guide
Testing
I have performed tests described in the Contributing guide:
terraform applyterraform fmtcheckIntended location
Yes, this sample will be (or already is) included on cloud.google.com
Location(s): https://cloud.google.com/storage/docs/managing-lifecycles#terraform
No, this sample won't be included on cloud.google.com
Reason:
API enablement
Review