Menu
Use when syncing code, database, or files between local and Acquia Cloud environments, or pulling a Cloud database/files locally.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | pull-push |
| description | Use when syncing code, database, or files between local and Acquia Cloud environments, or pulling a Cloud database/files locally. |
| license | Proprietary |
| compatibility | acli>=2.x |
| metadata | {"category":"deployment","author":"Acquia","version":"1.0.0","tags":"acli, acquia-cloud, sync, deployment, database, files","software_requirements":"acli>=2.x"} |
Use when:
acli pull:all
Aliases: acli refresh, acli pull
Prompts you to select an environment, then copies code, database, and files to your local environment.
Options:
acli pull:all \
--dir=/path/to/project \
--no-code \ # skip code
--no-databases \ # skip database
--no-files \ # skip files
--no-scripts # skip post-pull scripts
acli pull:code
Pulls the latest code from the selected Cloud environment into your local directory.
acli pull:code --dir=/path/to/project
acli pull:database
Alias: acli pull:db
Imports a database backup from a Cloud environment into your local database.
Options:
acli pull:database \
--on-demand \ # force a fresh on-demand backup (not cached)
--no-import \ # download the backup file but don't import it
--multiple-dbs # download multiple databases (multisite)
acli pull:files
Copies Drupal public files (sites/default/files) from the Cloud environment to your local.
If you skipped scripts during a pull, run them separately:
acli pull:run-scripts
acli pull:run-scripts --dir=/path/to/project
acli push:database
Alias: acli push:db
Uploads your local database to a Cloud Platform environment. Requires both a local and remote database to be configured.
acli push:files
Copies your local Drupal public files to the selected Cloud environment.
acli push:code
Push code from your Cloud IDE to a Cloud Platform environment. This command is only available inside a Cloud IDE or Lando environment.
Build your project and push the compiled artifact to a Cloud environment or custom git remote:
acli push:artifact
Common options:
# Push to a specific branch on Cloud
acli push:artifact --destination-git-branch=deploy/main
# Push to a specific tag
acli push:artifact --destination-git-tag=release-1.2.3
# Push to an external git URL (e.g. GitHub)
acli push:artifact --destination-git-urls=git@github.com:myorg/myrepo.git
# Dry run — build but don't push
acli push:artifact --no-push
# Build in a specific directory
acli push:artifact --dir=/path/to/project
# Skip sanitization step
acli push:artifact --no-sanitize
acli pull:all
acli pull:database --on-demand
acli push:artifact --destination-git-branch=tags/deploy-branch
acli push:files
--on-demand for fresh data — The default pull uses a cached backup; --on-demand forces a new one.--no-push — Verify the artifact is correct before pushing.--no-scripts in CI — Post-pull scripts are designed for local dev, not CI pipelines.pull:all and pull:database require a running local database. Make sure your local Drupal stack (Lando, DDEV, etc.) is running.
Verify your SSH key is set up and your account has write access to the environment:
acli ssh-key:list
acli auth:me
Check that composer install and any build steps complete without errors before pushing:
acli push:artifact --no-push # dry run to inspect