single demo runner for AD/EntraID/ExchangeOnline + LifecycleEvent Joiner/Mover/Leaver

[blindzero]

Goal

• Make IdLE easy to evaluate and run by providing one demo entrypoint that exercises real Joiner/Mover/Leaver flows across providers.

Scope

• Provide a single examples runner script (extend existing examples/Invoke-IdleDemo.ps1 or replace with a single canonical runner).
• Runner parameters (no legacy aliases):
  • -Provider AD | EntraID | ExchangeOnline
  • -LifecycleEvent Joiner | Mover | Leaver | All
  • -ConfigPath (provider-specific config)
  • -AllowDestructiveOperations (required for Delete operations; default false)
• Provide provider-specific example workflow definitions for:
  • AD: Joiner/Mover/Leaver
  • EntraID: Joiner/Mover/Leaver
  • ExchangeOnline: Leaver (focus), plus minimal Joiner/Mover if feasible
• Ensure secrets are never printed:
  • Example outputs must demonstrate that redaction works (no raw secrets in events/results).
• Provide copy/paste documentation for running each provider demo:
  • prerequisites, config template, and commands

Acceptance Criteria

• A user can run:
  • -Provider AD -LifecycleEvent All
  • -Provider EntraID -LifecycleEvent All
  • -Provider ExchangeOnline -LifecycleEvent Leaver
    using documented steps.
• Delete operations require explicit opt-in via -AllowDestructiveOperations.
• Demo output shows structured results and events without leaking secrets.

[blindzero]

Closing as superseded by #96.
The original goal of “a single demo runner” overlaps with the work in #96, which clarifies the separation between runnable demo workflows (mock) and templates/live workflows, and fixes the current discovery/listing behavior (e.g., -All should not enumerate non-runnable templates).
“Live without script edits” is not a meaningful target on its own because real environments always require explicit configuration (auth, tenant, endpoints, permissions). We will keep the demo runner focused on mock demos as defined in #96, and treat live/template execution as a separate concern (to be addressed via explicit config-driven entrypoints if needed).