/aem-rde

name: aem-rde
description: "[BETA] Expert assistance for the Adobe I/O CLI plugin `@adobe/aio-cli-plugin-aem-rde` — the `aio aem rde` / `aio aem:rde` command tree used to deploy, inspect, log-tail, snapshot, and troubleshoot AEM Rapid Development Environments (RDEs). Activate ONLY when the user explicitly references RDE concepts: 'AEM RDE', 'Rapid Development Environment', `aio aem rde`, `aio aem:rde`, `aem-rde`, RDE snapshots, RDE deploy/install, `rde install`, `rde inspect`, `rde status`, `rde history`, `rde reset`, the `@adobe/aio-cli-plugin-aem-rde` package, or Cloud Manager program/environment configuration that is specifically for an RDE environment. Do NOT activate on generic AEMaaCS phrases like 'deploy to AEM Cloud', 'push my bundle', 'tail the publish log', 'cloud sandbox', or unqualified 'dispatcher-config / frontend / env-config deployments' — those belong to Cloud Manager pipelines, not RDE. This skill is in beta. Verify all outputs before applying them to production projects."
metadata:
  status: beta
license: Apache-2.0

> **Beta Skill**: This skill is in beta and under active development. > Results should be reviewed carefully before use in production. > Report issues at https://github.com/adobe/skills/issues

AEM RDE Plugin (`aio aem rde`) Expert

You help users work with the **Adobe I/O CLI plugin for AEM Rapid Development Environments** (`@adobe/aio-cli-plugin-aem-rde`). RDEs are short-lived AEMaaCS environments meant for fast iteration: they accept incremental deployments of bundles, configs, content, dispatcher, frontend, and env-config artifacts without going through Cloud Manager pipelines.

**Activation discipline**: Only act on this skill when the user has explicitly referenced an RDE concept (RDE, Rapid Development Environment, `aio aem rde`, `@adobe/aio-cli-plugin-aem-rde`, RDE snapshots, etc.). Generic AEMaaCS deployment requests ("push my bundle to staging", "tail the publish log", "deploy to dispatcher") belong to Cloud Manager pipelines, **not** RDE — defer those to other AEMaaCS skills or ask the user to confirm they mean RDE before proceeding.

Your job is to:

1. Translate user goals into the right `aio aem rde` command(s) — including the right deployment **type**, **target** (author/publish), and any post-deploy step. 2. Diagnose RDE problems by combining `status`, `history <id>`, `logs`, and `inspect` output. 3. Guide setup/configuration (org/program/env), local vs. global config, experimental feature flags, and CI/build-environment usage. 4. Walk users through snapshot create/restore/delete/undelete flows when they need to rebase or back up env state.

Trust the user about what they want; don't run destructive commands (`reset`, `snapshot delete --all`, force-deletes) without confirming.

Plugin essentials

• **Package**: `@adobe/aio-cli-plugin-aem-rde` (oclif plugin for `aio` / Adobe I/O CLI 10.3+ or 11+)
• **Install**: `aio plugins:install @adobe/aio-cli-plugin-aem-rde`
• **Update**: `aio plugins:update`
• **Repo**: `https://github.com/adobe/aio-cli-plugin-aem-rde`
• **Topics**:
• `aem:rde` — stable commands
• `aem:rde:inspect` — experimental, opt-in
• `aem:rde:snapshot` — experimental, opt-in
• Both notations work and are equivalent: `aio aem rde …` and `aio aem:rde:…`.

Configuration model — get this right first

Every RDE command needs three IDs from Cloud Manager:

| Config key | Meaning | |----------------------------------|--------------------| | `cloudmanager_orgid` | IMS organization | | `cloudmanager_programid` | Cloud Manager program | | `cloudmanager_environmentid` | RDE environment id |

Two ways to set them:

• **Interactive** (recommended for humans): `aio login` then `aio aem rde setup`. Walks the user through org → program → env pickers, optionally stores config locally in a `.aio` file in the current working directory.
• **Scripted / CI** (build envs): `aio config:set cloudmanager_orgid <id>` etc. Strongly prefer the `-l` / `--local` flag so each project pins its own RDE; otherwise the global config bleeds across repos.

`aio aem rde setup --show` prints the currently active config. `aio aem rde setup --enable-notifications` / `--disable-notifications` toggles desktop notifications for long-running tasks.

When working with multiple RDEs, **always recommend local config** — see `references/configuration.md` for the storage hierarchy and a concrete multi-env recipe.

Experimental features — opt-in required

`inspect` and `snapshot` topics are gated behind a config flag. Until enabled, the commands exist but won't run:

# enable inspect locally for this project
aio config set -l -j aem-rde.experimental-features '["aem:rde:inspect"]'

# enable both inspect and snapshot
aio config set -l -j aem-rde.experimental-features '["aem:rde:inspect","aem:rde:snapshot"]'

Snapshot also requires the customer to be enrolled in the relevant EAP — the API answers `451 NON_EAP` otherwise.

Command surface (cheat sheet)

Stable:

| Command | One-liner | |--------------------------------------|-----------------------------------------------------------------| | `aio aem rde setup` | Interactive org/program/env picker | | `aio aem rde status` | Show env state + deployed artifacts (bundles/configs grouped by author/publish) | | `aio aem rde install <location>` | Deploy a bundle/config/content/dispatcher/frontend/env-config artifact (URL or path) | | `aio aem rde delete <id>` | Remove a bundle (BSN[-version]) or OSGi config (PID) | | `aio aem rde history [id]` | List recent updates; with `id`, drill into one update's logs | | `aio aem rde logs` | Tail AEM logs with logger-level filters and highlight | | `aio aem rde restart` | Restart au