Reference
Lookup material for Cloud Platform, down to the exact command, key, event, or limit.
acli commandsEvery acli command, routed by task and grouped by use case: full entries with flags and defaults for the commands the guides rely on, plus global flags, environment variables, and configuration files.
Pipelines build definitions
Section titled “Pipelines build definitions”Pipelines is driven by one file, acquia-pipelines.yaml; the quickstart reaches a first green run and the CI/CD guide covers triggers, secrets, and promotion.
| I want to… | Open |
|---|---|
Look up an acquia-pipelines.yaml key, its allowed values, or its defaults |
Creating and managing your build definition file on docs.acquia.com |
| Start from a working, annotated example file | Example build definition files on docs.acquia.com |
See every variable a job gets (BUILD_DIR, PIPELINE_VCS_PATH, CI, …) |
Default environment variables on docs.acquia.com |
| Check the job container’s limits (timeout, memory, disk, concurrency) | Resources for Pipelines jobs on docs.acquia.com |
| Encrypt a credential or SSH key for the build definition file | Encrypting keys and variables on docs.acquia.com |
Install the pipelines client |
Installing the Pipelines client on docs.acquia.com |
Pick a php service version the runner supports, or get a PHPUnit step to bootstrap Drupal |
Pipelines quickstart |
Cloud Hooks
Section titled “Cloud Hooks”Cloud Hooks are the scripts the platform runs on deploy events; the code-workflow guide shows where they sit in the deploy loop and a worked drush deploy hook.
| I want to… | Open |
|---|---|
| Look up a hook event’s positional arguments | Supported hooks in the acquia/cloud-hooks repository |
Check the hooks/ directory layout and execution order |
The Cloud Hooks directory in the acquia/cloud-hooks repository |
| Check the Cloud Next limits, or what a hook may safely contain | Automating with Cloud Hooks on docs.acquia.com |
| Start from a working script | The samples directory in the acquia/cloud-hooks repository |
Code Studio Auto DevOps
Section titled “Code Studio Auto DevOps”Code Studio pipelines are configured through CI/CD variables and an acquia_config.yaml at the project root; the CI/CD guide covers when to choose it over the recommended surfaces.
| I want to… | Open |
|---|---|
Look up an Auto DevOps variable (ACQUIA_JOBS_*, ACQUIA_TASKS_*, NODE_*) |
Using environment variables on docs.acquia.com |
| See what each Drupal pipeline stage runs | Drupal Auto DevOps jobs on docs.acquia.com |
See what each Node.js pipeline stage runs, or look up acquia_config.yaml keys |
Node.js Auto DevOps jobs on docs.acquia.com |
Deploy an artifact my own CI built, with enable-prebuilt-artifact |
Deploy from your own CI/CD, and Configuring external CI/CD on docs.acquia.com |
Was this page helpful?
What went wrong?
Still stuck? Contact Acquia Support (opens in a new tab)