Share a scenario with a teammate
Goal: pass a reproducible scenario to another person without overwriting their catalog.
Export
Section titled “Export”From the scenario’s menu (or Settings for the full catalog), Export generates a
self-contained file <scenario>.microlab.yml with:
- The scenario.
- The manifests of its micros (with the branch each repo is on).
- The referenced mocks.
- Optionally, each micro’s startup configuration (toggle “Include startup
configuration”), sanitized: credentials travel as a
${creds.x}reference and absolute paths are omitted.
Your settings.local.yml and the .runtime/ state do not travel.
Import
Section titled “Import”On the other machine, Import scenarios opens a reconciliation dialog: the import never overwrites bluntly, it resolves conflict by conflict with the recommended option preselected.
- A scenario that already exists enters as a copy (never overwritten).
- A manifest that differs: keep local (default), use the incoming one, or view the diff.
- The mocks: union by endpoint+variant.
If referenced repos are missing in the workspace, MicroLab warns: the scenario is imported, but it won’t launch until you clone them.
From the CLI
Section titled “From the CLI”microlab scenario export <name> [--include-run] and microlab scenario import <file> [--apply] [policies] (without --apply it prints the conflict plan).