agentleFS
acquiaacquia/acquia-skills/skills/acli/meo-overview/SKILL.md

meo-overview

Skill10 starsChanged 38 days agoMITView on GitHub

Use when determining whether to use ACE (V2) or MEO (V3) commands, or when starting work on a MEO multi-site subscription for the first time.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    How to tell which type a subscription is: Look at the available commands.

    line 36
  2. Very specific:

    No separate login is needed.

    line 73

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

MEO (Multi-site Enterprise Operations) Overview

Use when:

  • Determining whether a subscription uses ACE or MEO
  • Starting work on a MEO multi-site subscription
  • Choosing between acli api:* (ACE) and acli api:v3:* (MEO) commands
  • Discovering which MEO commands are available

ACE vs MEO — Choosing the Right Commands

Acquia Cloud Platform has two subscription types, each with its own API and CLI command prefix:

ACE (Acquia Cloud Enterprise)MEO (Multi-site Enterprise Operations)
CLI prefixacli api:*acli api:v3:*
API versionV2 (cloud.acquia.com/api)V3 (api.acquia.com/v3)
ModelOne application → multiple environments, one Drupal site per environmentSubscription → Codebases + Environments → Sites → Site Instances (many Drupal sites per environment)
Use caseSingle-site per environmentMultiple Drupal sites sharing an environment

How to tell which type a subscription is: Look at the available commands. If acli api:v3:sites:list returns results, it is MEO. If acli api:applications:list is the primary entry point, it is ACE.


MEO Resource Model

Subscription
├── Codebases (shared git repos)
│   └── References (branches / tags)
└── Environments (runtime containers)
    ├── Site Instances (one per Site per Environment)
    │   ├── Domains
    │   └── Database + Backups
    └── Deployments (code deploy operations)

Sites (logical Drupal sites, linked to a Codebase)
    └── Site Instances (a Site deployed into an Environment)

Key relationships:

  • A Codebase holds the shared git repository
  • A Site is the logical definition of a Drupal site, referencing a Codebase
  • An Environment is where code runs (prod, staging, dev, etc.)
  • A Site Instance is a Site running inside an Environment (has its own database and domain)

Authentication

MEO uses the same Acquia Cloud credentials as ACE:

acli auth:login
acli auth:me

No separate login is needed. The api:v3:* commands automatically use the V3 API endpoint (https://api.acquia.com/v3).

For scripts and CI/CD:

export ACLI_KEY="$ACQUIA_KEY"
export ACLI_SECRET="$ACQUIA_SECRET"
acli api:v3:sites:list

Store the credentials in your secrets manager or CI platform as ACQUIA_KEY/ACQUIA_SECRET; export them as ACLI_KEY/ACLI_SECRET for the step that runs acli — that's the name ACLI itself reads.


Discovering MEO Commands

MEO commands are generated dynamically from the V3 API spec. To see all currently available commands:

# List all V3 namespaces
acli list api:v3

# List commands for a specific resource
acli list api:v3:sites
acli list api:v3:codebases
acli list api:v3:environments
acli list api:v3:site-instances
acli list api:v3:deployments
acli list api:v3:subscriptions
acli list api:v3:failover-groups
acli list api:v3:identity-providers
acli list api:v3:sso-domains
# Get full help for any command (parameters, examples)
acli api:v3:sites:list --help
acli api:v3:sites:create --help

As new endpoints are added to the V3 API spec, they appear automatically in acli list api:v3 — no skill update required.


Command Stability

StabilityMeaning
productionStable, fully supported
developmentAvailable but may change; use with awareness

Current production-stable namespaces: sites, codebases, core subscription commands.

Development-stability namespaces: environments, site-instances, deployments, failover-groups, subscriptions (security/CDN), identity-providers, sso-domains.


Quick Start: Find Your Resources

# Find sites you have access to
acli api:v3:sites:list

# Find codebases for a subscription
acli api:v3:subscriptions:list-codebases <subscriptionId>

# Find environments for a codebase
acli api:v3:codebases:list-environments <codebaseId>

# Find site instances in an environment
acli api:v3:environments:list-site-instances <environmentId>

Related MEO Skills

  • MEO Sites — Create, update, duplicate, delete sites
  • MEO Codebases — Manage codebases and git references
  • MEO Environments — Environment operations, protection mode, deployments
  • MEO Site Instances — Site instance lifecycle, domains, databases
  • MEO Deployments — Monitor and control deployments
  • MEO CDN & Security — CDN, IP rules, custom rules, rate limiting
  • MEO Identity & Access — SSO domains, identity providers

ACE Skills (V2 only)

  • Application Management — ACE applications
  • Environment Management — ACE environments
  • Pull & Push — ACE code/DB/file sync

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.