CloudRun: wait until revision is deployed

[mszewczyk-ipwt]

Currently If a pulumi_google_native.run.v1.Service is declared and pulumi is updating resources then the update is finished before revision is up and traffic is rerouted. This can result in false information about CloudRun service updated while on the GCP side it can still fail, because the service is not up and running.

Example timeline with failed service:

1. Begin update
2. Pulumi is applying revision
3. GCP is starting to apply revision
4. Pulumi has finished applying revision
5. Pulumi has finished update - exit code 0
6. GCP is rolling new revision
7. GCP has failed to rollout the revision

Finally Pulumi has no information that revision has failed to update.

If there was a way to declare the provider to wait until the traffic is rerouted, then the Pulumi would have the information about failed deployment.

[mikhailshilkov]

Thank you for reporting! I think this has the same cause as #35

[steren]

It is expected for clients to fetch the status of the Cloud Run revision deployment by polling the status field of the Service object.

[viveklak]

Fixed in #411