sales-demos-factslisted

Gather, cache and publish a demo guest's Ansible facts — a curated summary in the job log, the full set in AAP's database, and a report at <web_url>/facts.html. Launches Linux Day 2 - Gather Facts or Windows Day 2 - Gather Facts in AAP, or the Day 1 step 5 that does the same work as part of a build. TRIGGER when: the user asks to gather or refresh facts, wants to show AAP's fact cache or a host's Facts tab, asks what AAP knows about a VM, says the Facts tab is empty or stale, wants the fact report republished, or asks about issue #647 or #648. SKIP: if the user wants to build a VM from nothing — that is sales-demos-provision — or wants the CIS compliance report, which is sales-demos-ocpvirt-demo.
ericcames/sales.demos · ★ 1 · Web & Frontend · score 67

Install: claude install-skill ericcames/sales.demos

# sales-demos-facts Make AAP's fact cache visible. The full `ansible_facts` set lands in AAP's database, a curated summary prints in the job log, and the same summary is published as a page on the guest — so the Facts tab and the artifact a customer can curl say the same thing. **This skill contains no logic.** The work is in [`playbooks/roles/demo_facts`](../../../playbooks/roles/demo_facts), included by [`playbooks/check_linux_vm.yml`](../../../playbooks/check_linux_vm.yml) and [`playbooks/check_windows_vm.yml`](../../../playbooks/check_windows_vm.yml). ## First: which OS? | | Linux | Windows | |---|---|---| | Group | `linuxweb` | `windemo` | | Day 2 template | `Linux Day 2 - Gather Facts` | `Windows Day 2 - Gather Facts` | | Day 1 step that also does it | `Linux Day 1 - 5 Check and Gather Facts` | `Windows Day 1 - 5 Check and Gather Facts` | | Credential | `Sales Demos - Linux Machine` | `Sales Demos - Windows Machine` | | Transport | SSH, port 22 | WinRM/NTLM, port 5986 | | Docroot | `/var/www/html` | `C:\inetpub\wwwroot` | Ask the cluster when it is not obvious: ``` mcp__openshift-<env>__resources_list kubevirt.io/v1 VirtualMachine namespace: sales-demos-<env> ``` ## Nothing writes the cache, and that is the point `gather_facts: true` in the playbook plus `use_fact_cache: true` on the job template is the **entire** mechanism. Do not go looking for the task that pushes facts to AAP — there isn't one, and saying so out loud is half the demo. It is also why this