You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2019. It is now read-only.
Currently, cloud-run-button uses REPO_NAME as container image repository and Cloud Run service name. It seems not to be configurable.
Because Cloud Run forbids service name which starts with a number, cloud-run-button is not compatible with some GitHub Gist repository.
ERROR: (gcloud.beta.run.deploy) INVALID_ARGUMENT: The request has errors
- '@type': type.googleapis.com/google.rpc.BadRequest
fieldViolations:
- description: Service name must use only letters, numbers and '-'. Must begin with
a letter and cannot end with a '-'. Maximum length is 63 characters.
field: metadata.name
If it is configurable, cloud-run-button become GitHub Gist compatible.
It works well and I have noticed SERVICE_NAME is prefixed by x in some cases.
I want to confirm SERVICE_NAME generation rule.
Is SERVICE_NAME created as like below?
SERVICE_NAME=$(echo $REPO_NAME | sed -e 's/[^a-z0-9\-]//g' | sed -E 's/^([0-9])/x\1/')
Currently, cloud-run-button uses REPO_NAME as container image repository and Cloud Run service name. It seems not to be configurable.
Because Cloud Run forbids service name which starts with a number, cloud-run-button is not compatible with some GitHub Gist repository.
Ref: https://gist.github.com/apstndb/63022c10ca5e94ed6e7c1dff9d5dbeaf
The text was updated successfully, but these errors were encountered: