Gcloud in Google Cloud SDK 0.9.57 breaks application deployment

Question

Starting on 04/22/15, updating gcloud to the latest version aborts the deploy command. The application version is set to the current time stamp (for example: 20150422t202108). And do:

gcloud preview app deploy . 

returns an error

 "ERROR: Directories are not supported [.]. You must provide explicit yaml files." 

And deploying the application using separate .yaml files complains about the version specified in the module, because the update sets the version of the application to a timestamp.

 "The version [1] declared in [/Users/username/app.yaml, /Users/username/app2.yaml] does not match the current gcloud version [20150422t202108]." 

Is this an error or have the configuration settings changed? I do not see the differences on the documentation page.

Answer 1

The deployment version is now explicitly and never taken from your yaml files. Two cases are possible:

1) If you use the -version flag, any version you use is used. This is an error if it does not match the values ​​in your yaml file.

2) If you do not use the -version flag, a version number is generated for you. This is the error you see, because, again, the version does not match the one in your yaml file.

The correct solution here is to simply remove the version attribute from your yaml (instead of trying to match them).

The deploy command also no longer accepts directories as arguments. You specify the yaml files that you want to deploy explicitly.

Answer 2

• gcloud preview app team behavior has changed, see updated page
• Can you confirm that the version is set to the timestamp in both yaml configurations? Try installing the version manually using the --version flag

Answer 3

Can you try the following command to deploy the application

gcloud preview app deploy ~ / my_app / app.yaml

and for an application having a different module

gcloud preview app deploy ~ / my_app / app.yaml \

~ / my_app / another_module.yaml