No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Does anyone have any advice for how to configure the dependency tree for ManagedSslCertificates with GKE Ingresses? I feel like with a couple of tweaks, I could figure out how to avoid a situation where Pulumi tries to delete it without first unasssigning it from the Ingress.

```-   └─ gcp:compute:ManagedSslCertificate  xxxxcert     **deleting failed**     1 error
Diagnostics:
  gcp:compute:ManagedSslCertificate (xxxxcert):
    error: deleting urn:pulumi:beta:xxxxxxx$gcp:compute/managedSslCertificate:ManagedSslCertificate::xxxxcert: 1 error occurred:
    	* Error when reading or editing ManagedSslCertificate: googleapi: Error 400: The ssl_certificate resource 'projects/xxx/global/sslCertificates/xxxxx-db58988' is already being used by 'projects/xxxxxx/global/targetHttpsProxies/xxxx-p0u1vzx7', resourceInUseByAnotherResource (edited) ```