create-landing-zone

Type: regulative

Decision

A landing zone must be provisioned through requestNew-Landing-Zone, and for a registered platform member.

Why

Provisioning outside the workflow leaves the subscription unaccounted for in the bank and off the application invoice section.

Violations

• Landing zone provisioned for an application with no platform member file.
• Subscription created new while the bank held an empty one.

Anchor

no-platform-ops

Implements

• landing-zone

Steps

1. Confirm the application file exists under platform-members/. If not, register-platform-member completes first.
2. Collect from the user: application name, environment (test or prod), management group name (oases-prod or oases-test), and budget (optional, default 100).
3. Auto-select the subscription ID: az account management-group subscription show-sub-under-mg --name subscription-bank --query "[0].name" -o tsv
4. Confirm the values with the user, including the auto-selected subscription ID, then trigger the workflow, which raises a pull request.
5. A platform engineer reviews and approves the pull request, and that approval triggers the automation to complete provisioning.

Files

• platform-members/
• .github/workflows/requestNew-Landing-Zone.yml

Links

• register-platform-member (depends-on) — Provisioning has no application to target until the member profile, group, and billing scope exist.
• application-teams-own-the-cost (governed-by)
• landing-zone-ipam (governed-by)
• landing-zone-template (governed-by)
• deployment-branch-gated-promotion (governed-by)

← Back to knowledge graph