tenant-bootstrap

Automating MozCloud tenant bootstrap involves a guided multi-phase workflow that orchestrates staged PRs, approvals, and post-bootstrap tasks across infra and GPA repos to ensure a production-ready deployment.

The process for updating CODEOWNERS during tenant onboarding involves automated PR scaffolding that creates branches, applies template edits, commits changes, and prepares reviewer-ready PR bodies with push prompts for user confirmation.

Before bootstrapping a new MozCloud tenant, you need to collect inputs including app_code, function, risk_level, workgroup, workgroup_status, and an optional Jira ticket, which undergo pre-flight validations and generate derived values.

The tenant bootstrap workflow supports PR automation by scaffolding branches and preparing reviewer-ready PR bodies, coordinating with Atlantis and Terraform infra repos for staged approvals and applies.

Yes, you can use this guided workflow to generate tenant YAML for production deployments, as it enforces safe, auditable steps and covers input collection through final infra apply.

Limitations of automating tenant bootstrap include relying on user confirmation for push prompts and adhering to enforced safe, auditable steps, meaning it requires strict prerequisite and constraint compliance rather than fully autonomous execution.