application-management
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.
Works with
---
name: application-management
description: 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.
license: MIT
---
# Managing Applications
Use when:
- Listing applications you have access to
- Linking or unlinking a local repo to a Cloud application
- Creating a new Drupal or Next.js project
- Checking branch/tag deployment status
- Waiting for an async task to complete
- Exporting a full site archive
---
## List Applications
```bash
acli api:applications:list
```
Returns a JSON array of all applications you have access to. Each entry includes `id`, `uuid`, `name`, `type`, `status`, and `organization`.
To display a readable table:
```bash
acli api:applications:list | python3 -c "
import json, sys
apps = json.load(sys.stdin)
for a in apps:
print(f\"{a['id']:<10} {a['name']:<40} {a.get('type',''):<10} {a.get('status',''):<10}\")
"
```
---
## Open Application in Browser
```bash
acli app:open
```
Aliases: `acli open`, `acli o`
Opens the selected Cloud application in your default browser.
---
## Link and Unlink a Local Repository
Associate your local checkout with a Cloud application so commands like `env:deploy` can detect the app automatically:
```bash
cd /path/to/project
acli app:link
```
To remove the association:
```bash
acli app:unlink
```
---
## Tail Application Logs
Stream live logs from a Cloud environment:
```bash
acli app:log:tail
```
Prompts for the application and environment, then tails all available log streams in real time. Useful for monitoring deployments or debugging live issues.
---
## Check Branch and Tag Deployment Status
```bash
acli app:vcs:info
```
Lists all branches and tags in the application's git repository along with which environment (if any) each is currently deployed to.
---
## Wait for an Async Task
Some Cloud operations (database copies, environment mirrors) return a notification UUID. Wait for them to complete:
```bash
acli app:task-wait <notification-uuid>
```
Useful in CI/CD pipelines to block until a task finishes before proceeding.
---
## Create a New Local Project
Scaffold a new Drupal or Next.js project from an Acquia-recommended template:
```bash
# Interactive — prompts for template and directory
acli app:new:local
# Non-interactive
acli app:new:local my-project --template=acquia_drupal_recommended
acli app:new:local my-project --template=acquia_drupal_cms
```
Alias: `acli new`
Available templates:
- `acquia_drupal_recommended` — Standard Acquia Drupal project
- `acquia_drupal_cms` — Acquia Drupal CMS project
---
## Migrate from Drupal 7
Generate a new Drupal 9+ project from an existing Drupal 7 application using Acquia Migrate Accelerate:
```bash
acli app:new:from:drupal7
```
Options: `--drupal7-directory`, `--drupal7-uri`, `--stored-analysis`, `--recommendations`, `--directory`
Aliases: `acli ama`, `acli from:d7`
---
## Export a Site Archive
Export an application's code, files, and database as a single archive file:
```bash
acli archive:export /path/to/destination/
```
Options:
```bash
# Exclude public files
acli archive:export /path/to/destination/ --no-files
# Exclude database
acli archive:export /path/to/destination/ --no-database
# Use a specific source directory
acli archive:export /path/to/destination/ --dir=/path/to/drupal
```
---
## Best Practices
1. **Link your repo** — Run `acli app:link` in every project checkout so app-aware commands work without extra flags.
2. **Check VCS status before deploying** — Use `acli app:vcs:info` to confirm the right branch is ready.
3. **Use `app:task-wait` in CI** — Ensures async Cloud operations complete before the next pipeline step runs.
---
## Related Topics
- **[Environment Management](../environment-management/SKILL.md)** — List environments, deploy, create CDEs
- **[Pull & Push](../pull-push/SKILL.md)** — Sync code, database, and files
- **[Remote Access](../remote-access/SKILL.md)** — SSH, Drush, and log tailing
- **[SSH Key Management](../ssh-key-management/SKILL.md)** — Secure access setupMore Deployment & CI/CD skills
azure-enterprise-infra-planner
microsoft/azure-skills
Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment', 'Azure Backup for VM workloads'. PREFER azure-prepare FOR app-centric workflows.
azure-kubernetes-app-deploy
microsoft/azure-skills
Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster, containerize app for Kubernetes, generate K8s manifests for Azure, set up CI/CD for AKS, my AKS deployment is failing safeguard checks, I have a Django/Express/Spring Boot app to run on AKS. DO NOT USE FOR: creating or provisioning an AKS cluster (use azure-kubernetes), assessing migration to AKS Automatic (use azure-kubernetes-automatic-readiness), or deploying to non-AKS targets like Web Apps, Container Apps, or Functions.
finetuning
microsoft/azure-skills
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file upload, calibrate grader, deploy fine-tuned model, evaluate fine-tuned model. DO NOT USE FOR: general model deployment without fine-tuning (use deploy-model), agent creation (use agents), prompt optimization without training (use prompt-optimizer).

