renaming image-copy-gcr to image-copy-gcp (#206)

I thought it made sense to update this example (which is useful and
works perfectly fine) to reflect recent changes to GCP's product
offerings. They [recently deprecated
GCR](https://cloud.google.com/artifact-registry/docs/transition/transition-from-gcr)
and the service will be totally shut down in 2025.

This PR updates the name of this example to `image-copy-gcp` and updates
other docs in this repository to reflect the change.

After updating it ✨ works on my machine ✨ but I may
very well have missed something important, so please test things out
yourself.

Signed-off-by: Mark Drake <mark@chainguard.dev>

.github/workflows/build-push.yaml

@@ -22,7 +22,7 @@ jobs:
           - aws-auth
           - github-issue-opener
           - image-copy-ecr
-          - image-copy-gcr
+          - image-copy-gcp
           - image-diff
           - jira-issue-opener
           - slack-webhook

.github/workflows/build.yaml

@@ -15,7 +15,7 @@ jobs:
           - aws-auth
           - github-issue-opener
           - image-copy-ecr
-          - image-copy-gcr
+          - image-copy-gcp
           - image-diff
           - jira-issue-opener
           - slack-webhook

README.md

@@ -5,7 +5,7 @@ This repo holds a number of example apps demonstrating integrations with Chaingu
 - [GitHub Issue Opener](./github-issue-opener/README.md) - opens an issue in GitHub when a policy is violated
 - [Slack Webhook](./slack-webhook/README.md) - sends a message to a Slack channel when a policy is violated
 - [Jira Issuer Opener](./jira-issue-opener/) - opens an issue in Jira when a policy is violated
-- [GCR Image Copier](./image-copy-gcr/) - copies images to Google Container Registry when an image is pushed to cgr.dev
+- [GCP Image Copier](./image-copy-gcp/) - copies images to Google Artifact Registry when an image is pushed to cgr.dev
 - [ECR Image Copier](./image-copy-ecr/) - copies images to Amazon Elastic Container Registry when an image is pushed to cgr.dev
 - [AWS Auth Example](./aws-auth/) - demonstrates configuration of an AWS assumable Chainguard identity, as well as calling the Chainguard API from a Lambda function
 - [Tag History Example](./tag-history/) - demonstrates how to use the Chainguard API to track tag history for images in a registry

image-copy-gcr/README.md → image-copy-gcp/README.md

@@ -1,4 +1,4 @@
-# `image-copy-gcr`
+# `image-copy-gcp`
 
 This sets up a Cloud Run app to listen for [`registry.push` events](https://edu.chainguard.dev/chainguard/chainguard-enforce/reference/events/#service-registry---push) to a private Chainguard Registry group, and mirrors those new images to a repository in Google Artifact Registry.
 
@@ -9,7 +9,7 @@ it like this:
 
 ```
 module "image-copy" {
-  source = "github.com/chainguard-dev/platform-examples//image-copy-gcr/iac"
+  source = "github.com/chainguard-dev/platform-examples//image-copy-gcp/iac"
 
   # name is used to prefix resources created by this demo application
   # where possible.

image-copy-gcr/go.mod → image-copy-gcp/go.mod

@@ -1,4 +1,4 @@
-module github.com/chainguard-dev/platform-examples/image-copy-gcr
+module github.com/chainguard-dev/platform-examples/image-copy-gcp
 
 go 1.21
 

image-copy-gcr/iac/main.tf → image-copy-gcp/iac/main.tf

@@ -8,7 +8,7 @@ terraform {
 }
 
 locals {
-  importpath = "github.com/chainguard-dev/platform-examples/image-copy-gcr"
+  importpath = "github.com/chainguard-dev/platform-examples/image-copy-gcp"
 }
 
 provider "google" {