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

meo-deployments

Skill10 starsChanged 38 days agoMITView on GitHub

Use when monitoring, stopping, or terminating MEO deployments. Deployments represent a code deploy operation running in a MEO environment.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Note: All commands use acli api:v3:*.

    line 27
  2. Distinctive:

    Use when you want to safely interrupt a deployment that is taking too long or you've noticed an issue.

    line 87
  3. Very specific:

    Use only when stop is insufficient (e.g.

    line 100

≈ “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 Deployment Management

Platform: This skill applies to MEO (Multi-site Enterprise Operations) subscriptions only.

Use when:

  • Checking the status of a running or completed deployment
  • Stopping a deployment gracefully
  • Listing all deployments for an environment
  • Terminating a stuck deployment immediately

Starting a deployment: See MEO Environments — use acli api:v3:environments:create-deployment.

Note: All commands use acli api:v3:*. Run acli list api:v3:deployments to see all current deployment commands.


Start a Deployment

Deployments are started from the environment, not the deployment resource:

acli api:v3:environments:create-deployment <environmentId> <run_hooks> <code_reference>
# Deploy main branch with hooks enabled
acli api:v3:environments:create-deployment <environmentId> true refs/heads/main

# Deploy a tag without hooks
acli api:v3:environments:create-deployment <environmentId> false refs/tags/1.5.0

# Deploy with hook argument
acli api:v3:environments:create-deployment <environmentId> true refs/heads/main \
  --hooks_argument="production"

Returns a deploymentId to track progress.


Check Deployment Status

acli api:v3:deployments:find <deploymentId>

Returns status (pending, running, completed, failed, stopped, terminated), start time, and any error messages.


List Deployments for an Environment

acli api:v3:environments:list-deployments <environmentId>

Supports pagination and filtering:

acli api:v3:environments:list-deployments <environmentId> --limit=10 --sort=-created

Stop a Deployment

Sends a graceful stop request. The deployment finishes its current step and halts.

acli api:v3:deployments:stop <deploymentId>

Use when you want to safely interrupt a deployment that is taking too long or you've noticed an issue.


Terminate a Deployment

Destructive operation — explicit approval required. Immediately kills the deployment process regardless of current state. May leave sites in a partially deployed state. Confirm with the user before executing.

acli api:v3:deployments:terminate <deploymentId>

Use only when stop is insufficient (e.g. deployment is hung and unresponsive).


Code Deploy Concurrency

Controls how many site instances can be deployed in parallel within an environment:

# Get current setting
acli api:v3:environments:find-code-deploy <environmentId>

# Update concurrency
acli api:v3:environments:update-code-deploy <environmentId> <concurrency>

Typical Workflows

Deploy and monitor

# Start deployment
acli api:v3:environments:create-deployment <environmentId> true refs/heads/main

# Poll for completion (deploymentId returned above)
acli api:v3:deployments:find <deploymentId>

CI/CD pipeline deploy step

#!/bin/bash
set -e

DEPLOYMENT=$(acli api:v3:environments:create-deployment \
  "$ENV_ID" true "refs/heads/$BRANCH" --no-interaction)

DEPLOYMENT_ID=$(echo "$DEPLOYMENT" | python3 -c "import json,sys; print(json.load(sys.stdin)['id'])")

# Poll until complete
while true; do
  STATUS=$(acli api:v3:deployments:find "$DEPLOYMENT_ID" | \
    python3 -c "import json,sys; print(json.load(sys.stdin)['status'])")
  echo "Deployment status: $STATUS"
  case "$STATUS" in
    completed) echo "Deployment succeeded"; exit 0 ;;
    failed|stopped|terminated) echo "Deployment failed"; exit 1 ;;
  esac
  sleep 15
done

Discover More Commands

acli list api:v3:deployments
acli list api:v3:environments
acli api:v3:environments:create-deployment --help

Related Topics

  • MEO Overview — ACE vs MEO, data model
  • MEO Environments — Start deployments, manage environment settings
  • MEO Codebases — Find the git reference to deploy
  • MEO Site Instances — Verify site instance state after deployment

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.