environment-management — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited environment-management (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Platform: This skill applies to ACE (Acquia Cloud Enterprise) subscriptions only. For MEO (Multi-site Enterprise Operations), see MEO Environments.
Use when:
acli api:applications:environment-listShows all environments for an application (prod, staging, dev, and any CDEs).
acli env:infoShows PHP version, database, last deployment, URLs, and status for the selected environment.
CDEs are on-demand environments — useful for testing feature branches before merging.
acli env:create "My Feature Branch" feature/my-branchArguments:
label (required) — Human-readable name for the new environmentbranch (optional) — The git branch to deploy; prompts if omitted# Interactive (prompts for branch)
acli env:create "QA Review"
# Non-interactive
acli env:create "Sprint 42 Demo" release/sprint-42acli env:deletePrompts you to select the environment to delete. Only CDEs can be deleted; production and standard environments cannot.
acli api:environments:code-switch <environmentId> <branch>Example:
acli api:environments:code-switch 112927-9454a2b1-cce0-475e-ae5f-5374dbca9b0a masterReturns a notification UUID you can track with acli app:task-wait <uuid>.
Makes a destination environment identical to a source — copies code, database, files, and config.
acli env:mirror <source-environment> <destination-environment>Use environment aliases in the format app-name.env:
acli env:mirror myapp.prod myapp.stagingSkip specific components:
acli env:mirror myapp.prod myapp.staging \
--no-code \ # -c: skip code
--no-databases \ # -d: skip databases
--no-files \ # -f: skip files
--no-config # -p: skip configurationWarning: This overwrites the destination. All existing data in the destination environment is replaced.
Copy all cron tasks from one environment to another:
acli env:cron-copy <source_env> <dest_env>Example:
acli env:cron-copy myapp.prod myapp.stagingUseful after mirroring an environment to ensure scheduled tasks match.
acli env:certificate-create <certificate> <private-key>Options:
acli env:certificate-create \
/path/to/cert.pem \
/path/to/private-key.pem \
--label="My SSL Cert" \
--ca-certificates=/path/to/ca-bundle.pem \
--legacy # Use legacy SSL (non-SNI)To install from an existing CSR:
acli env:certificate-create cert.pem key.pem --csr-id=<csr-uuid># Create the environment
acli env:create "Feature: New Checkout" feature/new-checkout
# Mirror prod data to it
acli env:mirror myapp.prod myapp.<new-cde-id>acli env:mirror myapp.prod myapp.stagingacli api:environments:code-switch <prod-env-id> mainenv:cron-copy after mirroring to keep scheduled tasks in sync.Check available environments:
acli api:applications:environment-listCheck logs and retry. Use --no-databases or --no-files to skip the component that failed:
acli env:mirror myapp.prod myapp.staging --no-files~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.