jamesfredley commented on issue #561: URL: https://github.com/apache/grails-forge/issues/561#issuecomment-2864369181
Ultimately this was an issues with the newer version of `google-github-actions/setup-gcloud` and that was the simple path back to a working deploy. https://github.com/apache/grails-forge/commit/69d578cc0e0c10f0e9e9c78dc57500c2b7695ef3 A decent amount of work was done to publish to the GitHub container registry, if we ever want/need to revisit: https://github.com/apache/grails-forge/blob/fb76a5d4778a24bdb9ba7c4b21e991dd5d394815/.github/workflows/next-gcp-deploy.yml For now that would require more updates in GPC due to the following, so skipping that for now. ``` Run gcloud run deploy ***-next --image $IMAGE_NAME --region us-central1 --update-env-vars=HOSTNAME="next.grails.org",CORS_ALLOWED_ORIGIN="***",GITHUB_OAUTH_APP_CLIENT_ID=***,GITHUB_OAUTH_APP_CLIENT_SECRET=***,GITHUB_USER_AGENT=***,GITHUB_REDIRECT_URL=*** --platform managed --allow-unauthenticated --service-account= Deploying container to Cloud Run service [***-next] in project [***] region [us-central1] Deploying... failed Deployment failed ERROR: (gcloud.run.deploy) spec.template.spec.containers[0].image: Expected an image path like [host/]repo-path[:tag and/or @digest], where host is one of [region.]gcr.io, [region-]docker.pkg.dev or docker.io but obtained ghcr.io/apache/grails-forge/***:next. To deploy container images from other public or private registries, set up an Artifact Registry remote repository. See https://cloud.google.com/artifact-registry/docs/repositories/remote-repo. ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
