James Ward

Are you thinking for monorepos or for multirepo? Also, you could do this today with a pre/post create script, but that is kinda messy.

> What about adding support to specify image: in the app.json ? like this way the button could be anywhere..? Can you elaborate on that?

We do have deployment automated already: https://github.com/GoogleCloudPlatform/cloud-run-button/blob/master/cloudbuild-redirector.yaml So we could possibly add all the setup / deployment there.

With Jib right now we don't do the manual push because Jib does it for us. (I had just noticed that in the code.) For timing, here are the results...

Yeah, you are right that cloning over SSH isn't something we want to support. So we should fix that test and then don't actually need to do any secrets for...

Yeah, you are right that we don't want to replicate those other systems. So maybe we just keep it confined to a couple common things (GCS, Cloud SQL, Pub/Sub) or...

Here is a project that could use this: https://github.com/jamesward/nodebars Note that it is slightly more complicated than just provisioning Cloud SQL because I also need to setup the schema. Maybe...

Once we get pre/post create script support (#76) repos will be able to provision resources (Cloud SQL, buckets, service accounts, etc) but they will likely have to do it in...

Oh bummer. We could put a note in the docs indicating that branches containing a `/` aren't supported by the redirector.

That is strange because your home directory should have been empty when this ran (because it uses a custom image). Are you sure you used the Cloud Run Button image...