You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, according to the README, only the url is exposed as output. If the latestCreatedRevisionName was exposed as well, it could be used to do downstream checks for that specific revision.
Additional information
Would you accept a PR?
The text was updated successfully, but these errors were encountered:
+1 this would be extremely useful, especially when updating traffic in a subsequent step. Having an output for the created revision name would allow one to then have a step allocating all traffic to the newly deployed revision using the --to-revisions flag of gcloud run services update-traffic.
+1 this would be extremely useful, especially when updating traffic in a subsequent step. Having an output for the created revision name would allow one to then have a step allocating all traffic to the newly deployed revision using the --to-revisions flag of gcloud run services update-traffic.
TL;DR
When I deploy a service, I want to know which revision was deployed so that I can run downstream checks about it (e.g. is it ready?)
Detailed design
When invoking the cloud run command-line with format json (as this action does), the status output looks somewhat like this:
Currently, according to the README, only the url is exposed as output. If the
latestCreatedRevisionName
was exposed as well, it could be used to do downstream checks for that specific revision.Additional information
Would you accept a PR?
The text was updated successfully, but these errors were encountered: