rename capability groups to DNS-1123-safe hyphen form #21
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lab/iac!21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rename-capability-groups-hyphens"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Rename kanidm capability groups from
group-<app>_<capability>togroup-<app>-<capability>so one string serves as the kanidm group name, the k8s RoleBinding subject, and the k8s Role name.Why: the underscore form was illegal as a k8s object name (RFC 1123 — no underscores), forcing a second name for Roles/RoleBindings (
privatebin-developervsgroup-privatebin_developer) and a mental translation rule per capability. With hyphens, the object names, subjects, and kanidm groups all collapse to one token.Now is the cheap window: ADR-0006/0007 are still
proposedand the groups have no members yet — a rename is delete+recreate, costless while empty. The tofu-controller will reconcile the rename on next apply; existing underscore-named groups are recreated hyphenated.Files:
kanidm/modules/dev_groups/main.tf,README.md(naming convention),CONTEXT.md(domain note).Tracked work: prefactor for #7 (T4 k8s capability Roles) — the T4 branch's RoleBinding subjects already use the hyphen form and will match once this merges.