concept version in category cloud

This is an excerpt from Manning's book Google Cloud Platform in Action.
Cloud SQL is a VM that’s hosted on Google Compute Engine, managed by Google, running a version of the MySQL binary. This means that you get a perfectly compatible MySQL server that you don’t ever have to SSH into to tweak settings. Instead, you can change all of those settings in the Cloud Console, the Cloud SDK command-line tool, or the REST API. If you’re familiar with Amazon’s Relational Database Service (RDS), you can think of Cloud SQL as almost the same thing. And although Cloud SQL currently supports both MySQL and PostgreSQL, I’ll only discuss MySQL for now.
Versions themselves are a lot like point-in-time snapshots of a service. If your service is a bunch of code inside a single directory, a version of your service corresponds to the code in that directory at the exact time that you decided to deploy it to App Engine. A neat side effect of this setup is that you can have multiple versions of the same service running at the same time.
Similar to how the first App Engine service you deploy becomes the default service for your entire application, the code that you deploy in that first service becomes the default version of that service. You can address an individual version of any given service, like you can address an individual service of your application. For example, you can see your web application by navigating to webapp.my-list.appspot.com (or explicitly, default.webapp.my-list.appspot.com), or you can view a newly deployed version (perhaps called version v2, as in figure 11.5) by navigating to v2.webapp.my-list.appspot.com.
I’ve covered the organizational concepts of applications, services, and versions. Now let’s take a moment to look at an infrastructural one: instances.
If you want to update your default version, you can make your code changes and deploy it like you did before. In this example, you’ll update the code to say, “Hello from version 2!” Once the deployment completes, you can verify that everything worked as expected by trying to access the URL as before:
$ curl https://your-project-id-here.appspot.com Hello from version 2!This might look like you’ve accidentally blasted out the previous version, but if you inspect the list of versions again, you’ll see that the previous version is still there and serving traffic:
$ gcloud app versions list --service=default SERVICE VERSION TRAFFIC_SPLIT SERVING_STATUS default 20171001t160741 0.00 SERVING default 20171002t072939 1.00 SERVINGNotice that the traffic split between the two versions has shifted, and all traffic is pointing to the later version, with zero traffic being routed to the previous version. I’ll discuss this in more detail later on. If the version is still there, how can you talk to it? It turns out that just as you can access a specific service directly, you can access the previous version by addressing it directly in the format of <version>.<service>.your-project-id-here.appspot.com (or using -dot- separators for HTTPS):
$ curl http://20171002t074125.default.your-project-id-here.appspot.com Hello from version 3, which is not live yet!Once you see that the new version works the way you expect, you can safely promote it by migrating all traffic to it using the Cloud Console. To do this, you browse to the list of versions, check the version you want to migrate traffic to, and click Migrate Traffic at the top of the page (figure 11.9).