IssueTracker

We're hosting our website's static content in a Cloud Storage bucket.  Our CI/CD pipeline uses Deployment Manager to provision the bucket (along with other GCP services).  We also populate the bucket with our static contents.

Problem you have encountered:
When we amend the YAML not to include the bucket, DM tries and fails to remove the bucket due to the fact that it isn't empty.

"ResourceErrorMessage":{"code":409,"errors":[{"domain":"global","message":"The bucket you tried to delete was not empty.","reason":"conflict"}

What you expected to happen:
The bucket should be emptied and removed.
Compare this to the provisioning/deprovisioning of a database.  Would I expect DM to refuse to deprovision until I have emptied all the tables?

Steps to reproduce:
1) As the DM service account:  Deploy a YAML containing a storage.v1.bucket resource
2) As the DM service account:  Upload some files to the bucket
3) As the DM service account:  Remove the storage.v1.bucket resource from the YAML and update.

Other information (workarounds you have tried, documentation consulted, etc):

There is an related issue [1] which advises adding the "Storage Admin" role to your user and emptying the bucket that way.
You could also use the DM account to empty the bucket first.

Note:  This could also be solved by the Cloud Storage team adding a "force delete" option and DM using that.