Hello, You are right, you can use traffic splitting to specify a percentage distribution of traffic across two or more of the versions within a service, as detailed on the "Split Traffic" page <https://cloud.google.com/appengine/docs/standard/python/splitting-traffic>. Deploying with --promote would attract all traffic to the deployed version. However, by contrast, traffic splitting is applied to URLs that do not explicitly target a version. In other words, you'll need 2 separate services, one for your prod environment, the other for staging. Two versions would not work for traffic splitting.
You can access different versions by version URLs at any time. On Tuesday, 15 June 2021 at 08:28:05 UTC-4 [email protected] wrote: > > Hi, > I would like to understand the relation between --promote (--no-promote) > and split traffic. > > - When I make a version deployment (--promote), it means it takes 100% of > the traffic > - When I make a version deployment (--no-promote), it won't take any > traffic percentage. > *However, would I be able to visit this version by URL? Would this version > be stopped or active?* > - Split Traffic it works sort of against (--promote). We use it when we > want to split the traffic among versions instead of promoting a single > version. > > I am planning to have two versions of my app. One is prod and another > staging. > > Only prod should serve clients. While staging should only be used > internally for testing, etc. > > Shall I use *--promote* with the prod environment and *--no-promote* with > the staging one? > > Thanks > Bill > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/9d2dbb80-b62e-4f84-b372-5567ac7af1b6n%40googlegroups.com.
