From the observations I have seen from our application App Engine only provides the endpoints from the version which is set as default. When we deploy a new version including a new endpoint it's not available for clients when using Traffic Splitting.
0
votes
This is not the case, we recently added support for non-default versions. As for traffic splitting, what is the specific use case? Versioning your APIs is a much better solution than relying on traffic splitting.
– bossylobster
We usually use Traffic Splitting feature to provide version stickiness for our customers. Fred Sauer mentioned this approach here: stackoverflow.com/a/15417186/837709
– Nik Graf
What I currently do is: -- The Application is running under version 1 is set as default. It serves a Cloud Endpoints API with the version 0_0_1. -- Add a new API with the version 0_0_2 and add a new endpoint test. -- Update app.yaml to version 2 and deploy -- Turn on "Traffic Split" with 99% for version 2
– Nik Graf
My result: I don't see the API version 0_0_2 in the API Explorer and the 0_0_2 endpoint returns a 404 response
– Nik Graf
What's the recommended way to upgrade to a new version using Cloud Endpoints?
– Nik Graf
