cloud-run-button

cloud-run-button copied to clipboard

Optional Build Logs

6

It is nice to default to the cleanliness of not displaying build logs, but it would be cool if the user could see them. I remember @ahmetb indicating it might...

jamesward

Fork repo and set up Continuous Deployment instead of one-shot deployment

3

The experience of the button is amazing: click, get something running. But that's how you should deploy software. That's great for demos or for one-shot images that don't have to...

steren

multiple apps with a single button

10

you know, a microservice/microlith thing as a button

matti

Add support for "buildpacks" field in app.json

5

ahmetb

Use Public Image Instead of Building One

2

If a project publishes a public container image then maybe the button should allow the skipping the build and just using the existing image. Via `app.json` like: ``` { "build":...

jamesward

Introduced in #149, the API for the project list includes all lifecycle types, including projects pending deletion. The list of projects should only be those with lifecycle == "ACTIVE" (this...

glasnt

Git Commit Sha in Container Image Tag

8

It'd be cool to put the git commit sha in the container image tag.

jamesward

Add Other Skip Configs

12

Today we have `build.skip` which skips all build steps but it'd be nice to be able to skip specific steps: ``` "build": { "skipdocker": false, "skipjib": false, "skippack": false }...

jamesward

Capture source context for build container image

5

Cloud Run will soon display information from the [Container Analysis API](https://cloud.google.com/container-registry/docs/reference/rest) related to the provenance of the deployed container image. Because the button literally deploys from GitHub, it would be...

steren

What Next?

3

So the user has deployed their first app, now what? Maybe help them setup GCB for CI/CD.

jamesward