I don't think that can be done like that.
You could deploy to a different appengine project by putting a different project id and then have beta.mywebsite.com
route to that project instead. The nice thing about this option is everything else would be isolated (i.e. no chance of your beta changes causing bad data in your production database, or tasks in your queues)
Another option would be to deploy to a different service within your project and use your dispatch.yaml
to route beta.mywebsite.com
to it https://cloud.google.com/appengine/docs/standard/python3/reference/dispatch-yaml
A third option would be to put beta
as your version-id, and have your DNS redirect beta.mywebsite.com
to beta-dot-your_project_id.appspot.com
. However, when the user goes to beta.mywebsite.com
they would ultimately see beta-dot-your_project_id.appspot.com
in the URL bar. Also, when you're ready to go live, you would want to redeploy and promote that new version id and not promote the beta
version-id.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…