← Back to daily report

gitlab-ci-cd.md

Changed on 2026-07-03 23:52:59 EST

Unified Diff

--- a/gitlab-ci-cd.md
+++ b/gitlab-ci-cd.md
@@ -22,7 +22,7 @@
 * **Automated implementation**: Turn issues into working code with a single command or mention
 * **Project-aware**: Claude follows your `CLAUDE.md` guidelines and existing code patterns
 * **Simple setup**: Add one job to `.gitlab-ci.yml` and a masked CI/CD variable
-* **Enterprise-ready**: Choose Claude API, Amazon Bedrock, or Google Vertex AI to meet data residency and procurement needs
+* **Enterprise-ready**: Choose Claude API, Amazon Bedrock, or Google Cloud's Agent Platform to meet data residency and procurement needs
 * **Secure by default**: Runs in your GitLab runners with your branch protection and approvals
 
 ## How it works
@@ -34,7 +34,7 @@
 2. **Provider abstraction**: Use the provider that fits your environment:
    * Claude API (SaaS)
    * Amazon Bedrock (IAM-based access, cross-region options)
-   * Google Vertex AI (GCP-native, Workload Identity Federation)
+   * Google Cloud's Agent Platform (GCP-native, Workload Identity Federation)
 
 3. **Sandboxed execution**: Each interaction runs in a container with strict network and filesystem rules. Claude Code enforces workspace-scoped permissions to constrain writes. Every change flows through an MR so reviewers see the diff and approvals still apply.
 
@@ -98,7 +98,7 @@
 After adding the job and your `ANTHROPIC_API_KEY` variable, test by running the job manually from **CI/CD** → **Pipelines**, or trigger it from an MR to let Claude propose updates in a branch and open an MR if needed.
 
 <Note>
-  To run on Amazon Bedrock or Google Vertex AI instead of the Claude API, see the [Using with Amazon Bedrock & Google Vertex AI](#using-with-amazon-bedrock-%26-google-vertex-ai) section below for authentication and environment setup.
+  To run on Amazon Bedrock or Google Cloud's Agent Platform instead of the Claude API, see the [Using with Amazon Bedrock and Google Cloud](#using-with-amazon-bedrock-and-google-cloud) section below for authentication and environment setup.
 </Note>
 
 ### Manual setup (recommended for production)
@@ -107,8 +107,8 @@
 
 1. **Configure provider access**:
    * **Claude API**: Create and store `ANTHROPIC_API_KEY` as a masked CI/CD variable
-   * **Amazon Bedrock**: **Configure GitLab** → **AWS OIDC** and create an IAM role for Bedrock
-   * **Google Vertex AI**: **Configure Workload Identity Federation for GitLab** → **GCP**
+   * **Amazon Bedrock**: **Configure GitLab** → **AWS OIDC** and create an IAM role for Amazon Bedrock
+   * **Google Cloud's Agent Platform**: **Configure Workload Identity Federation for GitLab** → **GCP**
 
 2. **Add project credentials for GitLab API operations**:
    * Use `CI_JOB_TOKEN` by default, or create a Project Access Token with `api` scope
@@ -152,7 +152,7 @@
 
 Claude locates the bug, implements a fix, and updates the branch or opens a new MR.
 
-## Using with Amazon Bedrock & Google Vertex AI
+## Using with Amazon Bedrock and Google Cloud
 
 For enterprise environments, you can run Claude Code entirely on your cloud infrastructure with the same developer experience.
 
@@ -164,10 +164,10 @@
 
     1. An AWS account with Amazon Bedrock access to the desired Claude models
     2. GitLab configured as an OIDC identity provider in AWS IAM
-    3. An IAM role with Bedrock permissions and a trust policy restricted to your GitLab project/refs
+    3. An IAM role with Amazon Bedrock permissions and a trust policy restricted to your GitLab project/refs
     4. GitLab CI/CD variables for role assumption:
        * `AWS_ROLE_TO_ASSUME` (role ARN)
-       * `AWS_REGION` (Bedrock region)
+       * `AWS_REGION` (Amazon Bedrock region)
 
     ### Setup instructions
 
@@ -178,7 +178,7 @@
     1. Enable Amazon Bedrock and request access to your target Claude models
     2. Create an IAM OIDC provider for GitLab if not already present
     3. Create an IAM role trusted by the GitLab OIDC provider, restricted to your project and protected refs
-    4. Attach least-privilege permissions for Bedrock invoke APIs
+    4. Attach least-privilege permissions for Amazon Bedrock invoke APIs
 
     **Required values to store in CI/CD variables:**
 
@@ -196,15 +196,15 @@
     Use the Amazon Bedrock job example above to exchange the GitLab job token for temporary AWS credentials at runtime.
   </Tab>
 
-  <Tab title="Google Vertex AI">
+  <Tab title="Google Cloud's Agent Platform">
     ### Prerequisites
 
-    Before setting up Claude Code with Google Vertex AI, you need:
+    Before setting up Claude Code with Google Cloud's Agent Platform, you need:
 
     1. A Google Cloud project with:
-       * Vertex AI API enabled
+       * Google Cloud's Agent Platform API enabled
        * Workload Identity Federation configured to trust GitLab OIDC
-    2. A dedicated service account with only the required Vertex AI roles
+    2. A dedicated service account with only the required Google Cloud's Agent Platform roles
     3. GitLab CI/CD variables for WIF:
        * `GCP_WORKLOAD_IDENTITY_PROVIDER` (full resource name)
        * `GCP_SERVICE_ACCOUNT` (service account email)
@@ -215,9 +215,9 @@
 
     **Required setup:**
 
-    1. Enable IAM Credentials API, STS API, and Vertex AI API
+    1. Enable IAM Credentials API, STS API, and Google Cloud's Agent Platform API
     2. Create a Workload Identity Pool and provider for GitLab OIDC
-    3. Create a dedicated service account with Vertex AI roles
+    3. Create a dedicated service account with Google Cloud's Agent Platform roles
     4. Grant the WIF principal permission to impersonate the service account
 
     **Required values to store in CI/CD variables:**
@@ -228,13 +228,13 @@
     Add variables in Settings → CI/CD → Variables:
 
     ```yaml theme={null}
-    # For Google Vertex AI:
+    # For Google Cloud's Agent Platform:
     - GCP_WORKLOAD_IDENTITY_PROVIDER
     - GCP_SERVICE_ACCOUNT
     - CLOUD_ML_REGION (for example, us-east5)
     ```
 
-    Use the Google Vertex AI job example above to authenticate without storing keys.
+    Use the job example above for Google Cloud's Agent Platform to authenticate without storing keys.
   </Tab>
 </Tabs>
 
@@ -277,12 +277,12 @@
 
 * Amazon Bedrock enabled with access to your chosen Claude model(s)
 * GitLab OIDC configured in AWS with a role that trusts your GitLab project and refs
-* IAM role with Bedrock permissions (least privilege recommended)
+* IAM role with Amazon Bedrock permissions (least privilege recommended)
 
 **Required CI/CD variables:**
 
-* `AWS_ROLE_TO_ASSUME`: ARN of the IAM role for Bedrock access
-* `AWS_REGION`: Bedrock region (for example, `us-west-2`)
+* `AWS_ROLE_TO_ASSUME`: ARN of the IAM role for Amazon Bedrock access
+* `AWS_REGION`: Amazon Bedrock region (for example, `us-west-2`)
 
 ```yaml theme={null}
 claude-bedrock:
@@ -319,22 +319,22 @@
 ```
 
 <Note>
-  Model IDs for Bedrock include region-specific prefixes (for example, `us.anthropic.claude-sonnet-4-6`). Pass the desired model via your job configuration or prompt if your workflow supports it.
+  Model IDs for Amazon Bedrock include region-specific prefixes (for example, `us.anthropic.claude-sonnet-4-6`). Pass the desired model via your job configuration or prompt if your workflow supports it.
 </Note>
 
-### Google Vertex AI job example (Workload Identity Federation)
+### Agent Platform job example (Workload Identity Federation)
 
 **Prerequisites:**
 
-* Vertex AI API enabled in your GCP project
+* Google Cloud's Agent Platform API enabled in your GCP project
 * Workload Identity Federation configured to trust GitLab OIDC
-* A service account with Vertex AI permissions
+* A service account with Google Cloud's Agent Platform permissions
 
 **Required CI/CD variables:**
 
 * `GCP_WORKLOAD_IDENTITY_PROVIDER`: Full provider resource name
 * `GCP_SERVICE_ACCOUNT`: Service account email
-* `CLOUD_ML_REGION`: Vertex region (for example, `us-east5`)
+* `CLOUD_ML_REGION`: Google Cloud's Agent Platform region (for example, `us-east5`)
 
 ```yaml theme={null}
 claude-vertex:
@@ -440,7 +440,7 @@
 ### Authentication errors
 
 * **For Claude API**: Confirm `ANTHROPIC_API_KEY` is valid and unexpired
-* **For Bedrock/Vertex**: Verify OIDC/WIF configuration, role impersonation, and secret names; confirm region and model availability
+* **For Amazon Bedrock or Google Cloud's Agent Platform**: Verify OIDC/WIF configuration, role impersonation, and secret names; confirm region and model availability
 
 ## Advanced configuration
 
@@ -451,8 +451,8 @@
 * `prompt` / `prompt_file`: Provide instructions inline (`-p`) or via a file
 * `max_turns`: Limit the number of back-and-forth iterations
 * `timeout_minutes`: Limit total execution time
-* `ANTHROPIC_API_KEY`: Required for the Claude API (not used for Bedrock/Vertex)
-* Provider-specific environment: `AWS_REGION`, project/region vars for Vertex
+* `ANTHROPIC_API_KEY`: Required for the Claude API (not used for Amazon Bedrock or Google Cloud's Agent Platform)
+* Provider-specific environment: `AWS_REGION`, project/region vars for Google Cloud's Agent Platform
 
 <Note>
   Exact flags and parameters may vary by version of `@anthropic-ai/claude-code`. Run `claude --help` in your job to see supported options.