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
This can be worked around by adding another step that does:
run: gcloud run services update-traffic ${{service}} --region ${{region}} --to-latest
The current situation is suboptimal because:
the user needs to duplicate the service and region parameters (or factor them out in variables) that are also used by the main deploy step
it's hard to discover because the deploy-cloudrun page doesn't mention this issue of using --no-traffic
Detailed design
Expose a to_latest value that if true will cause the action to call update-traffic with the --to-latest flag, similarly how presence of the revision_traffic and tag_traffic values already do
Additional information
No response
The text was updated successfully, but these errors were encountered:
TL;DR
When using
no_traffic: true
once, it's hard to set the trafficDocs for
--no-traffic
state:This can be worked around by adding another step that does:
The current situation is suboptimal because:
--no-traffic
Detailed design
Expose a
to_latest
value that iftrue
will cause the action to callupdate-traffic
with the--to-latest
flag, similarly how presence of therevision_traffic
andtag_traffic
values already doAdditional information
No response
The text was updated successfully, but these errors were encountered: