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

feat!: soft-delete configuration #309

Merged
merged 6 commits into from
Apr 10, 2024

Conversation

SHA65536
Copy link
Contributor

@SHA65536 SHA65536 commented Apr 4, 2024

Closes #301
I'm new to contributing so I hope I did all that is needed
Tested this on our infra

@SHA65536 SHA65536 requested a review from a team as a code owner April 4, 2024 12:07
Copy link

google-cla bot commented Apr 4, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Copy link
Member

@bharathkkb bharathkkb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bharathkkb bharathkkb changed the title feat: soft-delete configuration feat!: soft-delete configuration Apr 4, 2024
@SHA65536
Copy link
Contributor Author

SHA65536 commented Apr 7, 2024

@bharathkkb Let me know if there's something else I need to do? I don't know how to properly update the metadata

@bharathkkb
Copy link
Member

/gcbrun

@bharathkkb bharathkkb merged commit 1be844a into terraform-google-modules:master Apr 10, 2024
4 checks passed
@jdub55
Copy link

jdub55 commented Jun 3, 2024

@bharathkkb can you help explain the reason for min provider 5.22 for this change? Can this be backported to a 4.x version of the provider? Can we get this change backported to 4.x ? IHAC that is using 4.x of the provider and they need this change to be implemented on 4.x as otherwise they will need to upgrade to 5.x of the provider which will be a large and cumbersome task.

@SHA65536
Copy link
Contributor Author

SHA65536 commented Jun 4, 2024

This option does not exist on 4.x and defaults to a retention of 7 days, which will result in additional costs starting august

@victorcadena
Copy link

@SHA65536 it looks like it does for version 4.85.0, or is this a bug in the docs? https://registry.terraform.io/providers/hashicorp/google/4.85.0/docs/resources/storage_bucket#soft_delete_policy

@SHA65536
Copy link
Contributor Author

@victorcadena Hey, 4.85.0 came out 6 days ago, and they added the soft delete policy to there (2 months after the original pr, and 1 week after my last comment)
That means we no longer need 5.x as minimum version
Feel free to open a PR reducing the minimum version :)

@victorcadena
Copy link

victorcadena commented Jun 18, 2024

#321

Let me know if it is that simple or there are more considerations! @SHA65536

@SHA65536
Copy link
Contributor Author

Actually just noticed, the early 5.x versions (until 5.22) don't have soft delete, so I don't know how can we force >4.85 while also having <5.22
Maybe one of the maintainers can decide

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.

Support for configuring soft-deletes in GCS buckets
4 participants