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
I manually changed traffic rules and afterwards the action won't automatically deploy new revisions to be the latest serving revision. The CLI has a command to automatically make latest the serving revision, it would be great if there was a parameter for the github action called force_latest that would force the latest revision to be the serving revisios by using this command:
gcloud run services update-traffic [[SERVICE] --to-latest
The text was updated successfully, but these errors were encountered:
I was looking at the implementation, to add this feature, but from what I saw, think it should already be possible to manage the traffic of the latest revision, as far as I understand.
If either of the revision_traffic or tag_traffic options is set, the code builds a base command similar to the one suggested by @samos123.
Then, in the documentation of gcloud it is stated that one can always refer to the latest revision with LATEST.
Setting revision_traffic to LATEST=100 should do the trick (though I have not checked it myself, yet)
I manually changed traffic rules and afterwards the action won't automatically deploy new revisions to be the latest serving revision. The CLI has a command to automatically make latest the serving revision, it would be great if there was a parameter for the github action called
force_latest
that would force the latest revision to be the serving revisios by using this command:The text was updated successfully, but these errors were encountered: