Google Cloud Container Registry to gcr.io (Artifact Registry) migration

[jamesfredley]

https://cloud.google.com/container-registry/docs/deprecations/container-registry-deprecation
It appears we need to make some adjustments to grails-forge.

The workflow is publishing to gcr.io,

grails-forge/.github/workflows/next-gcp-deploy.yml

Line 29 in 4a6eb29

IMAGE_NAME: gcr.io/${{ secrets.GCP_PROJECT_ID }}/${{ secrets.GCP_APP_NAME }}:next

, but the last image push was on March 5th before the March 18, 2025, Container Registry shut down.

grails-forge/.github/workflows/next-gcp-deploy.yml

Line 61 in 4a6eb29

- name: "📤 Push image to Google Cloud Container Registry"

- it fails here

https://github.com/apache/grails-forge/actions/runs/14782199815/job/41503639504 - failed run

I have confirmed that the GitHub secrets still exist for this repo with ASF Infra.

[matrei]

Should we also copy existing images in Container Registry to Artifact Registry?

After May 20, 2025, reading images from Container Registry is unavailable. Existing images in Container Registry are inaccessible.
Any images in Container Registry that haven't been copied to Artifact Registry are unavailable.

[jdaugherty]

Given that OCI still maintains the GCP hosting, can we ask them to help here?

[jamesfredley]

Yes, on asking OCI for assistance. Before reaching out to them I wanted to see if we had someone that knew GCP that would be more efficient in communicating about this change with OCI. If we do not, I will handle it, since I worked with them on adding the additional environments for start.grails.org.

[jamesfredley]

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. 69d578c

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.