-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
switch deletion_policy to virtual field for google_firebase_web_app #6738
switch deletion_policy to virtual field for google_firebase_web_app #6738
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. Terraform GA: Diff ( 65 files changed, 82 insertions(+), 81 deletions(-)) |
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. Terraform GA: Diff ( 65 files changed, 82 insertions(+), 81 deletions(-)) |
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.
I just wanted to call to attention that this change makes the field updatable. I think that's a positive thing- there's no reason it had to recreate the resource in the first place, and recreation would have actually been undesirable imo. That meant there was no way to change the deletion policy without doing a deletion!
It looks like the normal generator save url-param-only already accounts for this.
Fields present in the API aren't a problem because their values get read during the refresh prior to plan. They do actually cause issues if you do a provider upgrade and then a refreshless plan, but that's an uncommon move and the fix is expensive (doing a lot of state upgrades).
url_param_only
is really meant to serve a specific purpose, fields in the URL that will never change, but the functionality is useful so it got used for other purposes. That was part of the motivation for introducing the virtual field override in the first place!
Tests analyticsTotal tests: Action takenTriggering VCR tests in RECORDING mode for the tests that failed during VCR. Click here to see the failed testsTestAccFirebaserulesRelease_BasicRelease|TestAccFirebaseWebApp_firebaseWebAppBasicExample |
Tests passed during RECORDING mode: Tests failed during RECORDING mode: Please fix these to complete your PR |
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. Terraform GA: Diff ( 14 files changed, 82 insertions(+), 26 deletions(-)) |
Tests analyticsTotal tests: Action takenTriggering VCR tests in RECORDING mode for the tests that failed during VCR. Click here to see the failed testsTestAccFirebaserulesRelease_BasicRelease|TestAccFirebaseWebApp_firebaseWebAppBasicExample |
Tests passed during RECORDING mode: Tests failed during RECORDING mode: Please fix these to complete your PR |
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. Terraform GA: Diff ( 14 files changed, 82 insertions(+), 26 deletions(-)) |
description: | | ||
Set to `ABANDON` to allow the WebApp to be untracked from terraform state | ||
rather than deleted upon `terraform destroy`. This is useful becaue the WebApp may be | ||
serving traffic. Set to `DELETE` to delete the WebApp. Default to `ABANDON` |
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.
serving traffic. Set to `DELETE` to delete the WebApp. Default to `ABANDON` | |
serving traffic. Set to `DELETE` to delete the WebApp. Defaults to `ABANDON`. |
@@ -54,6 +54,15 @@ overrides: !ruby/object:Overrides::ResourceOverrides | |||
org_id: :ORG_ID | |||
ignore_read_extra: | |||
- project | |||
- deletion_policy |
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.
We may want to call out something about importing the field in the docs, i.e.
Upon import, this field will always take on the default value of
"ABANDON"
, regardless of what's specified in configuration. If you have another value set, a diff will appear interraform plan
. Runterraform apply
to apply that value.
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.
this seems like not a great experience - would this be possible for us to fix / do we already have a ticket open to fix it?
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.
Tests analyticsTotal tests: Action takenTriggering VCR tests in RECORDING mode for the tests that failed during VCR. Click here to see the failed testsTestAccFirebaserulesRelease_BasicRelease |
fyi @melinath: We'll want to hold/cherry-pick for this fix, or revert the original change |
* Make deletion_policy a virtual_field for AndroidApp and AppleApp similar to #6738 * Accomodate upstream comments and inconsistent patches
…gleCloudPlatform#6911) * Make deletion_policy a virtual_field for AndroidApp and AppleApp similar to GoogleCloudPlatform#6738 * Accomodate upstream comments and inconsistent patches
…gleCloudPlatform#6911) * Make deletion_policy a virtual_field for AndroidApp and AppleApp similar to GoogleCloudPlatform#6738 * Accomodate upstream comments and inconsistent patches
Fix for issues caused by #6652
This new field was forcing recreation due to not being set on READ.
abandon default forcing recreation.
Although, even adding a value with a default will break configurations since we don't read this value anywhere. This leads me to believe adding any value that has a default will encounter this unless it's set on read if the api doesn't return it. It looks like the normal generator save
url-param-only
already accounts for this.Switching to a virtual field resolved this.
Release Note Template for Downstream PRs (will be copied)