Running Against The Proof Lab

Running Against The Proof Lab

If you do not already have a safe Azure environment for demos or testing, use the companion proof lab:

• HarrierOps Azure OpenTofu Proof Lab

Use a disposable subscription you control. The lab is intentionally insecure and is meant for practice, validation, and walkthroughs.

Suggested Operator Flow

1. Build the lab by following the proof-lab repo instructions.
2. Authenticate to Azure.
3. Point Azure CLI at the lab subscription.
4. Run a small command first, then a current chain or flat-command follow-up.

Example Session

Authenticate and select the subscription:

az login
az account set --subscription <lab-subscription-id>

Confirm identity and visible subscription context:

ho-azure --outdir ./ho-azure-lab whoami --output table

Run an initial census:

ho-azure --outdir ./ho-azure-lab inventory --output table

Run the chain overview once the basics look right:

ho-azure --outdir ./ho-azure-lab chains --output table

If you want a narrower path-oriented pass first:

ho-azure --outdir ./ho-azure-lab chains credential-path --output table

Why The Lab Helps

• It gives you a known environment to validate command behavior.
• It makes screenshots and walkthroughs easier to reproduce.
• It reduces the temptation to learn HarrierOps Azure for the first time in a production tenant.

Practical Tip

Use a dedicated --outdir like ./ho-azure-lab so the resulting artifacts stay grouped together while you compare runs.