Thanks, Patrice, for the valuable information. In practice, I test and verify Staging. Once we are happy with it, we merge the "develop" branch on the "main" branch and then production takes the latest changes.
However, with versions, every new build of the app, could be a new version. Instead of making the new version --promote right away, we could make it --no-promote, then split the traffic so that both versions start receiving traffic, until the old version is stopped. Is this entire process of moving to the new version automated somehow? Or we have to do it manually? And what are the cons of just moving to a new version right away? On Tue, Jun 15, 2021 at 6:13 PM Patrice Bertrand < [email protected]> wrote: > Sure. Note that I'm just a regular user. > I think it is best if "versions" in terms of GAE deployment match > "versions" in terms of your Git, i.e. a consistent state of your project's > files. > Thus there will be occasions when you need to change version for your > production environment. In such cases you would deploy your new version > with --no-promote, then start the new version then migrate, or if you have > a heavy traffic with many instances started you would split traffic then > gradually increase the share sent to the new version, up to 100%, then stop > the previous version (or let it stop). Within your staging project (or > possibly 'service'), you might also need to handle versions, and a given > version might be deployed to the staging project and when validated, > deployed to the production project. So if you were using versions as > environments you would have very little flexibility in managing actual > versions. > Patrice > > > On 6/15/21 4:42 PM, Bilal Haidar wrote: > > Thanks Patrice! > > Can you explain to me or refer me to a resource on the real use of > versions? I must have misunderstood it. > > Many thanks > Bilal > > On Tue, Jun 15, 2021 at 5:34 PM Patrice Bertrand < > [email protected]> wrote: > >> Hello Bill, >> >> Maybe you should consider using 2 distincts projects instead of versions >> for the need that you describe. This will allow you to use versions as >> proper versions, and to handle a version change within a given service. >> >> Alternatively, you could consider using 2 services, each with versions as >> needed. >> >> Using different projects or different services of a project should not >> affect your costs, since you are paying for live instances ultimately. >> >> Patrice >> >> >> On 6/15/21 2:28 PM, Bilal Haidar 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/bca3d802-dbea-43ee-8348-43c0ad3007a5n%40googlegroups.com >> <https://groups.google.com/d/msgid/google-appengine/bca3d802-dbea-43ee-8348-43c0ad3007a5n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Google App Engine" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/google-appengine/kJO6TBILzxI/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/google-appengine/6e7bd439-3cd2-abff-7abd-0462ca1f0620%40gmail.com >> <https://groups.google.com/d/msgid/google-appengine/6e7bd439-3cd2-abff-7abd-0462ca1f0620%40gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > 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/CAFDSF-2zBPCZaqdkH_Bv-n7BvYkiDXLXv%2BKAgf4U2%2BnqGBw1oA%40mail.gmail.com > <https://groups.google.com/d/msgid/google-appengine/CAFDSF-2zBPCZaqdkH_Bv-n7BvYkiDXLXv%2BKAgf4U2%2BnqGBw1oA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > > -- > [image: logo ExperQuiz] Patrice Bertrand > Directeur Associé > 06 60 11 00 09 > www.experquiz.com > > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Google App Engine" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-appengine/kJO6TBILzxI/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-appengine/eabe2497-3242-0876-d32a-75cb34112554%40experquiz.com > <https://groups.google.com/d/msgid/google-appengine/eabe2497-3242-0876-d32a-75cb34112554%40experquiz.com?utm_medium=email&utm_source=footer> > . > -- 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/CAFDSF-1hF6vzbX7AvSStLYxijsdgkk4WXOMkNtw71BLgypqAfw%40mail.gmail.com.
