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
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
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 <
patrice.bertrand...@gmail.com> wrote:
> Hello Bill,
>
> Maybe you should consider using 2 distincts
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
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
