Skip to content

docs: add "Install a scenario pack and its adapter" guide - #1249

Closed
Brad-Edwards wants to merge 1 commit into
devfrom
docs/install-scenario-packs
Closed

Brad-Edwards wants to merge 1 commit into
devfrom
docs/install-scenario-packs

Conversation

@Brad-Edwards

Copy link
Copy Markdown
Collaborator

Summary

Document how LilRAE installs and runs a scenario, which is two parts: the content pack and its adapter. This came up while onboarding TechVault from env-packs: the existing getting-started docs do not explain the pack-plus-adapter model, the env-pack scenario source, or why --scenario <id> only accepts the configured pack.

The guide covers

  • The two parts: the pack (content, resolved from the installed raes-env-packs by identity) and the adapter (the aptl.* entry points keyed by the pack id; aptl_techvault ships in lilrae).
  • Installing each part.
  • Selecting the pack in aptl.json (scenario.source: env-pack, scenario.identity).
  • Verifying with aptl lab scenarios and running with aptl lab start.
  • Troubleshooting: unknown scenario id, missing pack distribution, missing adapter.

Added to the Lab Guide nav. Vale-clean.

Document how LilRAE consumes a scenario as two installed parts: the content
pack (resolved from raes-env-packs by identity) and its adapter (the aptl.*
entry points keyed by the pack id). Cover selecting the pack in aptl.json,
verifying with aptl lab scenarios, and troubleshooting unknown-id,
missing-pack, and missing-adapter errors. Add it to the Lab Guide nav.
@Brad-Edwards

Copy link
Copy Markdown
Collaborator Author

Folded into #1248 (consolidated so the two PRs the repo-wide security fix touches don't need cross-branch ledger juggling). The install-packs guide is included there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant