Assigned
Status Update
Comments
kn...@google.com <kn...@google.com> #2
Hello,
Thank you for reaching out to us!
This issue seems to be outside of the scope of Issue Tracker. This Issue Tracker is a forum for end users to report bugs
and request features
on Google Cloud products. Please go through
I recommend you to
For now, I'm going to close this thread which will no longer be monitored. In case you want to report a new issue, please do not hesitate to create a new Issue Tracker describing your issue.
Thank you!
Description
We'd really love to not have to choose! That is, we'd love to be able to use `--migrate` when moving from one multi-version split to another. This would help us minimize the impact on our site from moving traffic to a new version.
To be explicit, we would like to be able to run (assuming we start with all traffic on v1):
gcloud app deploy --version v2
gcloud app services set-traffic --migrate v1=95,v2=5
gcloud app services set-traffic --migrate v1=90,v2=10 # a minute later
gcloud app services set-traffic --migrate v1=85,v2=15 # another minute later
and so on. Right now, this fails with error messages like "ERROR: (gcloud.app.services.set-traffic) The migrate flag can only be used with splits to a single version." (The equivalent option in the Cloud Console UI is also disabled.)