Skip to content

Onboard talos-cluster: rulesets in-band + required checks (P0.3) - #79

Open
NWarila wants to merge 1 commit into
mainfrom
onboard-talos-cluster-ruleset
Open

Onboard talos-cluster: rulesets in-band + required checks (P0.3)#79
NWarila wants to merge 1 commit into
mainfrom
onboard-talos-cluster-ruleset

Conversation

@NWarila

@NWarila NWarila commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Onboards nwarila-platform/talos-cluster into the framework (P0.3) so its repo settings + the Branch Safety / Pull Request Gate / Release Tag Protection rulesets are Terraform-managed in-band, and adds enforced required status checks.

  • Rulesets: framework defaults verified 2026-07-12 to match the repo's current manual rulesets exactly (signing + linear history + squash-only + code-owner review + admin bypass) → adoption preserves all protection.
  • Required checks: Config Audit, Gitleaks Secret Scan, org-adr / verify — only checks that run on every PR. Path-filtered Validate checks deferred to Phase 2 (need an always-reports gate in validate.yaml, else doc-only PRs block).
  • Settings captured live to avoid drift; security features left unmanaged (already enabled).
  • Adoption (existing repo): runner must terraform import github_repository.repo["talos-cluster"] (+ the 3 rulesets if adopting) before first apply. The terraform plan here is the drift gate — review before applying.

…ired checks (P0.3)

Brings nwarila-platform/talos-cluster under Terraform management so its repo
settings and the Branch Safety / Pull Request Gate / Release Tag Protection
rulesets are managed in-band instead of configured out-of-band in the GitHub UI.
The framework default rulesets were verified 2026-07-12 to match the repo's
current manual rulesets exactly (signing + linear history + squash-only +
code-owner review + admin bypass), so adoption preserves all protection.

Adds required_status_checks using only checks that run on every PR (Config Audit,
Gitleaks Secret Scan, org-adr / verify); path-filtered Validate checks are Phase 2.
Existing-repo adoption: the runner must terraform import the repository (and the
rulesets if adopting) before the first apply; the plan on this PR is the drift gate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant