lab/iac
1
0
Fork 0
Code Issues 11 Pull requests 3 Projects Releases Packages Wiki Activity Actions

T1: Fix provider resolution + catalog schema (prefactor) #3

New issue
Closed
opened 2026-08-11 15:20:23 +00:00 by ginjiruu · 1 comment
ginjiruu commented 2026-08-11 15:20:23 +00:00
Owner
Copy link

Parent

Spec: catalog-driven app bootstrapping and capability groups (#2)

What to build

Make every root (forgejo, k8s, kanidm, vault) plan cleanly and settle the catalog schema that all other tickets read.

Acceptance criteria

  • forgejo root declares svalabs/forgejo with host/api_token and ~> 1.0 (has forgejo_team), not base_url/token/~> 0.2
  • k8s, kanidm, vault roots + every module declare their own required_providers so local provider names resolve (no hashicorp/forgejo mismatch)
  • tofu init + tofu validate succeeds in forgejo/, k8s/, kanidm/, vault/
  • catalog schema drops tiers → per-app capability-group list

Blocked by

None — can start immediately.

## Parent Spec: catalog-driven app bootstrapping and capability groups (#2) ## What to build Make every root (forgejo, k8s, kanidm, vault) plan cleanly and settle the catalog schema that all other tickets read. ## Acceptance criteria - [ ] forgejo root declares `svalabs/forgejo` with `host`/`api_token` and `~> 1.0` (has `forgejo_team`), not `base_url`/`token`/`~> 0.2` - [ ] k8s, kanidm, vault roots + every module declare their own `required_providers` so local provider names resolve (no `hashicorp/forgejo` mismatch) - [ ] `tofu init` + `tofu validate` succeeds in forgejo/, k8s/, kanidm/, vault/ - [ ] catalog schema drops `tiers` → per-app capability-group list ## Blocked by None — can start immediately.
ginjiruu commented 2026-08-11 15:35:00 +00:00
Author
Owner
Copy link

T1 verified complete: forgejo root uses svalabs/forgejo ~> 1.0 with host/api_token; all roots+modules declare required_providers; tofu init+validate green in forgejo/k8s/kanidm/vault; catalog schema drops tiers -> capability groups (ADR-0006/0007). Code-review passed both axes (minor follow-ups noted: lock-file policy consistency, modules/repos placeholder comment, group naming app-first vs capability-first to confirm in T2).

T1 verified complete: forgejo root uses svalabs/forgejo ~> 1.0 with host/api_token; all roots+modules declare required_providers; tofu init+validate green in forgejo/k8s/kanidm/vault; catalog schema drops tiers -> capability groups (ADR-0006/0007). Code-review passed both axes (minor follow-ups noted: lock-file policy consistency, modules/repos placeholder comment, group naming app-first vs capability-first to confirm in T2).
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
renovate/configure
t15-multicluster-catalog
t14-vault-k8s-auth
No results found.
Labels
Clear labels   
needs-info
Waiting on reporter for more information

  
needs-triage
Maintainer needs to evaluate this issue

  
ready-for-agent
Fully specified, ready for an AFK agent

  
ready-for-human
Requires human implementation

  
wontfix
Will not be actioned

No labels
needs-info
needs-triage
ready-for-agent
ready-for-human
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lab/iac#3
No description provided.