# Reference

Lookup material for Cloud Platform, down to the exact command, key, event, or limit.

- [acli commands](/cloud-platform/reference/acli/): Every 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

[Pipelines](/start-here/glossary/#pipelines) is driven by one file, `acquia-pipelines.yaml`; the [quickstart](/cloud-platform/ci-cd/quickstart/) reaches a first green run and the [CI/CD guide](/cloud-platform/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](https://docs.acquia.com/acquia-cloud-platform/creating-and-managing-your-build-definition-file) on docs.acquia.com |
| Start from a working, annotated example file | [Example build definition files](https://docs.acquia.com/acquia-cloud-platform/example-pipelines-build-definition-files) on docs.acquia.com |
| See every variable a job gets (`BUILD_DIR`, `PIPELINE_VCS_PATH`, `CI`, …) | [Default environment variables](https://docs.acquia.com/acquia-cloud-platform/default-environment-variables-pipelines) on docs.acquia.com |
| Check the job container's limits (timeout, memory, disk, concurrency) | [Resources for Pipelines jobs](https://docs.acquia.com/acquia-cloud-platform/resources-pipelines-jobs) on docs.acquia.com |
| Encrypt a credential or SSH key for the build definition file | [Encrypting keys and variables](https://docs.acquia.com/acquia-cloud-platform/encrypting-keys-and-variables) on docs.acquia.com |
| Install the `pipelines` client | [Installing the Pipelines client](https://docs.acquia.com/acquia-cloud-platform/installing-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-platform/ci-cd/quickstart/) |

## Cloud Hooks

[Cloud Hooks](/start-here/glossary/#cloud-hooks) are the scripts the platform runs on deploy events; the [code-workflow guide](/cloud-platform/code-workflow/guide/#automate-deploy-events-with-cloud-hooks) 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](https://github.com/acquia/cloud-hooks#supported-hooks) in the acquia/cloud-hooks repository |
| Check the `hooks/` directory layout and execution order | [The Cloud Hooks directory](https://github.com/acquia/cloud-hooks#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](https://docs.acquia.com/acquia-cloud-platform/automating-cloud-hooks) on docs.acquia.com |
| Start from a working script | [The samples directory](https://github.com/acquia/cloud-hooks/tree/master/samples) in the acquia/cloud-hooks repository |

## Code Studio Auto DevOps

[Code Studio](/start-here/glossary/#code-studio) pipelines are configured through CI/CD variables and an `acquia_config.yaml` at the project root; the [CI/CD guide](/cloud-platform/ci-cd/guide/) covers when to choose it over the recommended surfaces.

| I want to… | Open |
| --- | --- |
| Look up an [Auto DevOps](/start-here/glossary/#auto-devops) variable (`ACQUIA_JOBS_*`, `ACQUIA_TASKS_*`, `NODE_*`) | [Using environment variables](https://docs.acquia.com/acquia-cloud-platform/add-ons/code-studio/using-environment-variables) on docs.acquia.com |
| See what each Drupal pipeline stage runs | [Drupal Auto DevOps jobs](https://docs.acquia.com/acquia-cloud-platform/add-ons/code-studio/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](https://docs.acquia.com/acquia-cloud-platform/add-ons/code-studio/nodejs-auto-devops-jobs) on docs.acquia.com |
| Deploy an artifact my own CI built, with `enable-prebuilt-artifact` | [Deploy from your own CI/CD](/source-cms/deploy/external-ci/), and [Configuring external CI/CD](https://docs.acquia.com/acquia-cloud-platform/add-ons/node-js/configuring-external-cicd) on docs.acquia.com |