メニュー
Use when finding a pipelines application ID or linking a repo before running any pipelines-cli command that needs --application-id.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when user asks about updating outdated Drupal packages, upgrading Drupal core minor or patch versions, updating contrib modules, or resolving composer version conflicts.
Use when user asks about fixing security vulnerabilities, composer audit failures, vulnerable Drupal packages, or CVE advisories in a Drupal codebase.
Use when user wants to update Drupal dependencies and deploy the changes to an Acquia environment, optionally triggering a pipeline build. Chains drupal-maintenance, acli, and pipelines-cli skills.
Use when listing Acquia Cloud applications, linking or unlinking a local repo to an application, opening an app in browser, checking VCS/branch deployment status, or exporting a site archive.
Use when setting up a new Code Studio (GitLab CI/CD) project, changing PHP version in Code Studio builds. NOT for checking pipeline job status — use pipelines-cli-pipeline-operations for that.
Use when listing, creating, deleting, or mirroring Cloud environments, managing CDEs, deploying code to an environment, or checking environment status.
| name | application-management |
| description | Use when finding a pipelines application ID or linking a repo before running any pipelines-cli command that needs --application-id. |
| license | Proprietary |
| compatibility | pipelines-cli>=1.x |
| metadata | {"category":"deployment","author":"Acquia","version":"1.0.0","tags":"pipelines-cli, acquia-cloud, applications, codebases","software_requirements":"pipelines-cli>=1.x"} |
Use when:
Find application IDs associated with your account:
pipelines list-applications
Output:
Applications:
1g2i3b4b5o6u7s — My Drupal Site
abc1234567890 — Client Project
Use the application ID (e.g. 1g2i3b4b5o6u7s) in all subsequent pipeline commands.
List codebases available to your account (used as an alternative to application IDs):
pipelines list-codebases
Output:
+--------------------------------------+--------------+--------+--------------+
| Codebase ID | Label | Region | Applications |
+--------------------------------------+--------------+--------+--------------+
| abcd1234-5678-90ab-cdef-000000000000 | My Codebase | us-east| 3 |
+--------------------------------------+--------------+--------+--------------+
pipelines list-codebases --format=json
Codebase IDs can be used anywhere --application-id is accepted via the --codebase-id flag.
Associate your local git repository with an application or codebase ID. This lets you run pipelines start without specifying --application-id every time.
pipelines set-application-id --application-id=1g2i3b4b5o6u7s
Output:
The application id associated with this repository has been set to 1g2i3b4b5o6u7s
pipelines set-application-id --codebase-id=abcd1234-5678-90ab-cdef-000000000000
pipelines set-application-id --application-id=1g2i3b4b5o6u7s --format=json
The association is stored in the repository's git config. After linking, commands like pipelines start will detect the application ID automatically from the current directory.
Remove the application ID association from the current repository:
pipelines remove-application-id
| Application ID | Codebase ID | |
|---|---|---|
| Format | Short alphanumeric string | UUID |
| Scope | Single Acquia Cloud application | Can span multiple applications |
| Use when | Working with a specific application | Working with a shared codebase |
| Flag | --application-id | --codebase-id |
Both can be used interchangeably with start, status, logs, and list-jobs.
You haven't linked a repo or provided --application-id. Either:
# Option 1: Link the repo
pipelines set-application-id --application-id=<id>
# Option 2: Pass it explicitly each time
pipelines start --application-id=<id>
Your account doesn't have any codebases, or your credentials don't have access. Verify with:
pipelines show-connection <application_id>