Add Automation Job

Type: operation

Intent

The platform recognizes a repeating operational pattern and eliminates it — no landing zone ever needs a human for that task again.

Design Decisions

• landing-zone-automation
• platform-exemptions-automation
• landing-zone-identity

Steps

1. Read all design decisions in decisions[] to understand access, identity, and image constraints before writing any code.
2. Implement the job logic under landing-zones/automation/ — jobs must use the ARM API only; no data-plane or VNet-dependent calls.
3. Add a Dockerfile for the new image — base image must be pullable from a public registry without authentication.
4. Register the new job in landing-zones/bicep/modules/landingzone-automation.bicep following the existing job definition pattern.
5. Verify the job authenticates as the landing zone identity — no separate identity or secret.
6. Present a complete draft of all changes before implementing.

Files

• landing-zones/automation/
• landing-zones/bicep/modules/landingzone-automation.bicep

Violations

• implementing before reading all decisions

← Back to operations