-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Adds support for Filestore instance new feature: deletion protection. #11602
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
Adds support for Filestore instance new feature: deletion protection. #11602
Conversation
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 12 Click here to see the affected service packages
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
The failed VCR-test is due to API rollout changes that are in progress (should be finished very soon) and due to experiments not yet being fully ramped up yet. I'd appreciate a review regardless to move things forward in the meantime. |
Hello! I am a robot. Tests will require approval from a repository maintainer to run. @rileykarson, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look. You can help make sure that review is quick by doing a self-review and by running impacted tests locally. |
@rileykarson The experiments + API rollout dependencies that caused the test failure should be now resolved. Can you assist re-running the checks to validate all works? |
@rileykarson This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
/gcbrun |
1 similar comment
/gcbrun |
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 12 Click here to see the affected service packages
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly LGTM- one small test change to add an ImportState step after one of the Config steps.
I did want to flag that if we add a clientside deletion protection in the future we'll need to reconcile the fields [our thoughts on deletion_protection]. Given we don't have one I think this is still the right change to make anyways.
mmv1/third_party/terraform/services/filestore/resource_filestore_instance_test.go
Show resolved
Hide resolved
mmv1/third_party/terraform/services/filestore/resource_filestore_instance_test.go
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rileykarson back to you. Thanks
mmv1/third_party/terraform/services/filestore/resource_filestore_instance_test.go
Show resolved
Hide resolved
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 12 Click here to see the affected service packages
View the build log |
Users will be able to enable deletion protection on their new or existing Filestore instances by providing an instance's
deletion_protection_enabled
boolean field and optionally alsodeletion_protection_reason
string field specifying the reason for enabling the protection.Fixes hashicorp/terraform-provider-google#19336
Release Note Template for Downstream PRs (will be copied)