adds deletion_policy field generation to templates#16075
Conversation
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR hasn't generated any diffs, but I'll let you know if a future commit does. |
d2034ec to
f7577cc
Compare
|
Due to errors in #16076 from the size of the PR, swapping these generator changes to be done in product based batches. Following this PR I will bring the project flag into the swap PR, but maintain the need for it to be flagged true. Once all the product directories are merged into the feature branch, I will remove the project flag and there should be no diffs in this feature branch. |
… requires opting in via product)
|
brought the swap into this PR since it already has an opt-in gate via project, no reason for this change to be seperate due to the lack of diffs. |
|
🔴 The provider crashed while running the VCR tests in REPLAYING mode |
|
🔴 The provider crashed while running the VCR tests in REPLAYING mode |
|
🔴 The provider crashed while running the VCR tests in REPLAYING mode |
Tests analyticsTotal tests: 5987 Click here to see the affected service packages
Action takenFound 15 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
🟢 Tests passed during RECORDING mode: 🔴 Tests failed when rerunning REPLAYING mode: Tests failed due to non-determinism or randomness when the VCR replayed the response after the HTTP request was made. Please fix these to complete your PR. If you believe these test failures to be incorrect or unrelated to your change, or if you have any questions, please raise the concern with your reviewer. 🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
c2thorn
left a comment
There was a problem hiding this comment.
LGTM, acknowledging interim flag states
| // deletion_policy is a universal virtual attribute for managing the behavior of resources when a delete is attempted | ||
| // in Terraform. Because it is a virtual attribute, it needs to be excluded from these ImportStateVerifys. | ||
| if s.ImportStateVerify && !slices.Contains(s.ImportStateVerifyIgnore, "deletion_policy") { | ||
| s.ImportStateVerifyIgnore = append(s.ImportStateVerifyIgnore, "deletion_policy") |
There was a problem hiding this comment.
There's no harm in adding appending this, even if there's no deletion_policy field? I guess that's what we are already doing for labels?
There was a problem hiding this comment.
I don't believe so from the quick testing I did but I'll reverify toward the end. Worst case it does entail the excess of manual test updates.
592fb27
into
GoogleCloudPlatform:FEATURE-BRANCH-universal-deletion-policy
PR 1 of hashicorp/terraform-provider-google#25072
Adds ability to generate a deletion policy field via an opt-in flag.
Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.