Custody [secret_store] block for new dito installs (#92) #3

Merged
jsutter merged 1 commit from custody-secret-store-default into main 2026-07-31 18:39:37 +00:00
Owner

Part of #92 (P-1b). New dito installs bootstrap ~/.config/dito/config.toml with a [secret_store] block pointing at the operator-custody vault. Gated to dito only (ditc unchanged). No-clobber preserved. Mirrored in install.ps1. dit-operator holds the spec + CLI changes.

Part of #92 (P-1b). New dito installs bootstrap ~/.config/dito/config.toml with a [secret_store] block pointing at the operator-custody vault. Gated to dito only (ditc unchanged). No-clobber preserved. Mirrored in install.ps1. dit-operator holds the spec + CLI changes.
New dito installs now bootstrap ~/.config/dito/config.toml with a
[secret_store] block pointing at the operator-custody vault
(backend = openbao, addr + mount + token_path), so custody secrets are
host-independent by default. DITO_CUSTODY_ADDR overrides the custody
address; default is the documented custody endpoint.

Prints a next-steps notice: place the custody token at token_path (mode
0600) before the first tenant-converge, or converge fails at build_store.

Gated to the dito tool only (ditc configs unchanged). No-clobber
preserved: existing configs are never touched. Mirrored in install.ps1
for Windows parity (token_path expands via shellexpand_home at runtime).

Part of issue #92 P-1b (dit-operator repo holds the spec + CLI changes).
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
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
deepnet/dit-releases!3
No description provided.