sales-demos-orchestratorlisted

# sales-demos-orchestrator Installs Automation Orchestrator into an RHDP environment, database and all. Takes about **5 minutes**. This skill contains **no logic**. All the work is in [`playbooks/install_ao.yml`](../../../playbooks/install_ao.yml). See `CLAUDE.md` → *Skills and playbooks*. **`setup.yml` already runs this on every build**, so reach for this skill when you need it on its own: an environment built with `-e install_ao=false`, or an AO stack that needs reconciling without re-running CNV and the whole AAP configuration. ## What it does 1. Installs **CloudNativePG** (`certified-operators`, `stable-v1`) into `cnpg-system` with an AllNamespaces OperatorGroup. 2. Creates a single-instance PostgreSQL `Cluster` (`ao-db`, 10Gi) in `automation-orchestrator`, whose `initdb` makes the **backend** database. 3. Creates the other **two** databases as CNPG `Database` resources. 4. Reshapes CNPG's generated credentials into the two secrets the AO CRD wants. 5. Installs the **Automation Orchestrator operator** (`redhat-operators`, `stable`) and creates the `AutomationOrchestrator` CR with a Route. 6. Waits for `Ready=True`, then **asks the Route for a page** and requires a `200`. **Both operator Subscriptions use `installPlanApproval: Manual`** (#593). The playbook approves each operator's first InstallPlan, so a fresh install completes. It never approves an upgrade, so a new AO build cannot land unattended, which has already broken SSO once elsewhere. Manual doe