feat(repos): declare devantler-tech/kyverno-policies (shared Kyverno policy library)#94
Conversation
…policy library) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c78bc3f8dc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…olicies Codex P2s: the new repo declaration lacked the TeamRepository grant (ownership goes to teams) and the IssueLabels wiring, leaving it owner-only with default labels. Both follow the aws net-new pattern; kustomize renders the grant and all 22 canonical labels. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@codex review |
|
Codex Review: Didn't find any major issues. 👍 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Merged — thanks for promoting. The one-time org-admin bootstrap POST is the only remaining step (my unattended run cannot create a net-new public repo); one-click: gh api -X POST /orgs/devantler-tech/repos --input - <<'EOF'
{
"name": "kyverno-policies",
"description": "Shared Kyverno policy library for the devantler-tech platforms — the single source the platform and platform-template consume instead of vendoring per-repo copies.",
"visibility": "public",
"has_issues": true,
"custom_properties": {
"Type": "Infrastructure",
"EnableAutoMerge": "true",
"ScanGitHubActions": "true",
"AutomaticallyRequestCopilotCodeReview": "true",
"LintDocumentation": "false"
}
}
EOFAfter that the merged |
1 participant
Why
Both the platform and platform-template vendor their own Kyverno policy copies; platform-template's five oldest enhancement issues (platform-template#3–#7) have been gated for a month on the shared policy repo existing. Declaring it unblocks that whole theme.
What
Adds the
kyverno-policiesRepository + DefaultBranch CRs to the org's declarative repo config (net-new pattern copied fromaws.yaml, all-except-Delete policies).Operational note: after promotion, the repo needs the documented ONE-TIME org-admin bootstrap POST with the required custom properties (platform#2325 pattern) before the CR adopts it.
Part of platform-template#24 (theme 1)