add terraform-backend host to hosting-provider #882
No reviewers
fediversity/developers
Labels
No labels
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
blocked
component
api-service
component
fediversity-panel
component
nixops4
documentation
points
0
points
0.5
points
1
points
13
points
2
points
21
points
3
points
34
points
5
points
55
points
8
points
infinite
productisation
project-management
question
role
application-developer
role
application-operator
role
hosting-provider
role
maintainer
security
technical debt
testing
type
bug
type
deliverable
type
key-result
type
objective
type
task
type
unclear
type
user-story
user experience
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
fediversity/fediversity!882
Loading…
Reference in a new issue
No description provided.
Delete branch "kiara/fediversity:dev-terraform-backend"
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?
Adds a long-running shared
terraform-backend(nimbolus) deployed via the dev-CD path so production TF deployments can point at it as their state HTTP backend, as used in the tests.part of #515.
note that this still hard-codes various values, raising bootstrapping questions if infra like this was intended to hold such state (along with openbao, see #493).
bootstrap layering: seed → openbao-via-dev → SPIRE → workloads
Track the dependency chain that lets us remove deployment-specific data (e.g.
KMS_KEY_FILE, agenix recipients) from the codebase.Layering
examples/hosting-env-config.nix(gitignorable). Schema gains abootstrap/seedsub-attrset, explicitly marked bootstrap-only so we can audit which entries are still load-bearing as we climb the ladder. Prefer derived sources (TPM-sealed, generated-on-first-boot) where possible so seed entries stay minimal.Concrete follow-ups blocked on this
KMS_KEY_FILEonce openbao KMS is reachable (related: #515, #493).Out of scope here
Implementation of any single layer — this issue only captures the chain so each piece has a documented predecessor.
56158c1fca14385b8b6f14385b8b6f371b99f14cWIP: addto addterraform-backenddev hostterraform-backenddev hostaddto addterraform-backenddev hostterraform-backendhost tohosting-provider