Scott Suarez
Scott Suarez
This resource should support some sort of delete method, no? Otherwise there is no way to unset fields... if /delete/ in this case would mean an empty patch we should...
> @ScottSuarez I am curious how we want to handle terraform resource deletes in the case where the GCP resource does not support deletes ([cloud.google.com/resource-manager/docs/reference/resource-settings/rest](https://cloud.google.com/resource-manager/docs/reference/resource-settings/rest)). Is it customary to do...
The rest looks good, but check the link I posted. There is a specific way you want add warning to resources that properly will display the warning the user within...
Could the test be changed to update a trivial setting? Our SA's are using this organization and it has potential to crash our CI.
You could also target our alternative organization for these tests `ORG_TARGET` and `getTestOrgTargetFromEnv` respectively
Sorry, it looks like the CI system hasn't been configured with the new parameter yet so the test is unable to run. Let me run it locally to unblock.
I'm getting the following error running this locally ``` scottsuarez-macbookpro2:terraform-provider-google-beta scottsuarez$ make testacc TEST=./google-beta TESTARGS='-run=TestAccResourceSettingsOrganizationSetting_update' ==> Checking source code against gofmt... ==> Checking that code complies with gofmt requirements... TF_ACC=1...
What I imagine is going on is the resource will have to POST instead of PATCH if the key doesn't already exist?
Heya Riley, is this still relevant ?