drupal-update-deploy

Drupal Update and Deploy Workflow

Use when:

• Applying Drupal dependency updates and deploying to an Acquia environment
• Running the full cycle: update packages → push code → deploy → trigger pipeline

Prerequisites: The following skill sets must be loaded: drupal-maintenance, acli, pipelines-cli.

---

Workflow

Step 1 — Apply dependency updates

Ask the user: "Do you need to apply dependency updates first, or are updates already done?"

• If updates are needed → follow Security Updates or Dependency Updates depending on the use case, then return here.
• If updates are already applied → proceed to Step 2.

---

Step 2 — Fetch application and environments

Always run these before asking the user where to deploy. This ensures the correct application and environment IDs are used.

# List available applications and note the UUID
acli api:applications:list

Output shows application names and UUIDs. Ask the user: "Which application do you want to deploy to?" and confirm the UUID.

# List environments for the selected application
acli api:environments:list <app-uuid>

Output shows environment labels (dev, stage, prod, CDEs), IDs, and the currently deployed branch. Ask the user: "Which environment do you want to deploy to?"

---

Step 3 — Commit code changes

Before pushing, check for uncommitted changes:

git status

If there are uncommitted changes, ask the user: "Do you want to commit these changes before deploying?"

• If yes — ask for a commit message, then commit:

  git add -A
  git commit -m "<user-provided message>"
  

• If no — warn the user that uncommitted changes will not be included in the deployment and confirm they want to proceed.

---

Step 4 — Push code to Acquia Cloud

Push the committed code to the selected environment:

acli push:code