James Ward

There is a way to specify specific buildpacks via a `project.toml` file in the root: https://github.com/buildpacks/pack/pull/421

For continuing to work in Cloud Shell it'd be great to have some way to get the following pragmatically: - Source dir - Selected project - Selected region - Build...

Yeah, maybe if https://console.cloud.google.com/run/create had a way to specify some default params (image, service name, allow-unauthenticated, etc) then that'd be a better way to go. Still would be missing env...

Cool. By "capture" you just mean, let the user know more explicitly, or put that info somewhere?

Yeah, so maybe we just have to catch the failure and handle it with a better error message.

Maybe once a project is selected we can check perms, and if they aren't sufficient we ask them to select a different project. Or if we can't check the perms,...

Yeah, there could also be an `app.json` flag.

Yeah, the `app.json` creep is real. In this case we could disable the spinner. BTW, for some reason the spinner doesn't work (sometimes or all the time?). #182

One quick thought... if we want it to work on mostly existing machinery we could do: ``` { "env": { "SERVICE_ACCOUNT_EMAIL": { "description": "Service Account Email", "value": "$K_SERVICE@$GCP_PROJECT.iam.gserviceaccount.com", "required": true...

It's pretty easy with `envsubst` (which is in the cloud shell base image): ``` export K_SERVICE=foo; echo "asdf-$K_SERVICE" | envsubst ```