القائمة
Use when pipelines CLI is not installed, authentication fails, or user needs to set up pipelines-cli for the first time.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
| name | getting-started |
| description | Use when pipelines CLI is not installed, authentication fails, or user needs to set up pipelines-cli for the first time. |
| license | Proprietary |
| compatibility | pipelines-cli>=1.x |
| metadata | {"category":"onboarding","author":"Acquia","version":"1.0.0","tags":"pipelines-cli, acquia-cloud, ci-cd, installation, authentication","software_requirements":"pipelines-cli>=1.x"} |
Use when:
Two separate CLIs exist for Acquia Cloud operations:
| Tool | Purpose |
|---|---|
pipelines-cli | CI/CD pipeline operations: trigger builds, check job status, stream logs |
acli | General Cloud management: applications, environments, IDEs, SSH keys, code/DB sync |
Use pipelines-cli for pipeline jobs. Use acli for everything else.
wget https://cloud.acquia.com/pipelines-client/download -O pipelines
chmod +x pipelines
sudo mv pipelines /usr/local/bin
pipelines --version
pipelines help
pipelines configure
You will be prompted for your Acquia Cloud API key and API secret:
Please enter your Acquia Cloud API key: <your-key>
Please enter your Acquia Cloud API secret: <hidden>
Configuration successful.
Useful for CI/CD environments where interactive prompts are not available:
pipelines configure --key=YOUR_KEY --secret=YOUR_SECRET
Only needed if you are not using the default Acquia Cloud endpoint:
pipelines configure --key=YOUR_KEY --secret=YOUR_SECRET --endpoint=https://your-custom-endpoint.com
If your credentials change or you need to reconfigure:
pipelines reset-credentials
Then run pipelines configure again.
After configuring, confirm your environment is set up correctly:
pipelines show-connection <application_id>
Output confirms whether the connection and application access are working.
To find your application ID first:
pipelines list-applications
wget https://cloud.acquia.com/pipelines-client/download -O pipelines
chmod +x pipelines
sudo mv pipelines /usr/local/bin
pipelines configure
pipelines list-applications
pipelines show-connection <application_id>
pipelines start --application-id=<application_id>
pipelines self-update
Run this periodically to get bug fixes and new features.
# List all available commands
pipelines
# Help for a specific command
pipelines help start
pipelines help configure
# Version (include in bug reports)
pipelines --version
The binary is not in your PATH. Ensure you moved it to /usr/local/bin or another directory on your PATH:
which pipelines
export PATH="/usr/local/bin:$PATH"
Your API key or secret is incorrect. Verify them in the Acquia Cloud UI under API Keys, then re-run:
pipelines configure
When using --no-interaction, you must pass both --key and --secret:
pipelines configure --no-interaction --key=YOUR_KEY --secret=YOUR_SECRET
استنادا إلى تصنيف 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.
