"gcloud app deploy" automatically installs components app-engine-go since version 145.0.0

[Katherine Li]

I noticed that since version 145.0.0, the command "gcloud app deploy" automatically install the components "App Engine Go", "App Engine Go Extensions", and "gcloud app Python Extensions".

I have pasted below the terminal output of calling "gcloud app deploy" 

The installation did not happen in version 144.0.0.

I want to know if there is a way to get the old (144.0.0) behavior back?

Also, I am unsure where this change is mentioned in the release notes. Is it  referred to by the line

"gcloud app deploy now deploys Go apps for both Standard and Flexible environments. All usage of aedeploy can now use gcloud app deploy directly instead."?

-------------------------------------------------------

Beginning deployment of service [default]...
The component [app-engine-go] is required for staging this
application.


Your current Cloud SDK version is: 145.0.0
Installing components from version: 145.0.0

┌────────────────────────────────────────────────────┐
│        These components will be installed.         │
├───────────────────────────────┬─────────┬──────────┤
│              Name             │ Version │   Size   │
├───────────────────────────────┼─────────┼──────────┤
│ App Engine Go (Linux, x86_64) │  1.9.50 │ 47.9 MiB │
│ App Engine Go Extensions      │         │          │
│ gcloud app Python Extensions  │  1.9.50 │  7.2 MiB │
└───────────────────────────────┴─────────┴──────────┘

For the latest full release notes, please visit:
  https://cloud.google.com/sdk/release_notes

╔════════════════════════════════════════════════════════════╗
╠═ Creating update staging area                             ═╣
╠════════════════════════════════════════════════════════════╣
╠═ Installing: App Engine Go (Linux, x86_64)                ═╣
╠════════════════════════════════════════════════════════════╣
╠═ Installing: App Engine Go Extensions                     ═╣
╠════════════════════════════════════════════════════════════╣
╠═ Installing: gcloud app Python Extensions                 ═╣
╠════════════════════════════════════════════════════════════╣
╠═ Creating backup and activating new installation          ═╣
╚════════════════════════════════════════════════════════════╝

Performing post processing steps...done.

Update done!

Restarting command:
  $ gcloud -q app deploy app.yaml

[Steven Buss]

Hi Katherine, I'm afraid I don't quite understand the problem. As of gcloud 145.0.0 we do, indeed, automatically install the Go components when you try to deploy a Go app. What problems are you experiencing from this new behavior?

--
You received this message because you are subscribed to the Google Groups "google-appengine-go" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine-go+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Katherine Li]

Hi Steven,

I am working on a project, "Google App Engine Uploader", that uses the Google Cloud SDK to automate creating Google App Engine and deploying it. It uses the command "gcloud app deploy".

This behavior forces my project to be 55.1MB bigger than it was before, because now my users have to install these extensions as well.

Is there a way to deploy without installing Go (like the way it was before)?

To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine-go+unsubscribe...@googlegroups.com.

[Steven Buss]

You can force gcloud to use an old version of a component via `gcloud components update --version=144.0.0` but that will pin the version you use and distribute to your users, slowly falling further and further behind.

This automatic-install behavior is only triggered when your app is written in go and gcloud detects that it hasn't installed the go component. It should have been impossible to deploy a go app to App Engine without that component, so this auto-install behavior smooths out the user experience by installing necessary dependencies automatically. Are you saying that this is happening even when the app isn't go?