DRU-720 -- Sync managed services into the vault - #827
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
czpython
force-pushed
the
paulo/dru-720-manage-a-service-from-drukstoml
branch
from
October 4, 2026 18:32
753fed1 to
87c70e0
Compare
czpython
force-pushed
the
paulo/dru-720-manage-a-service-from-drukstoml
branch
from
October 4, 2026 18:45
87c70e0 to
d6e501d
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
A service that has a
[services.<slug>]table indruks.tomlis managed by deployment configuration. The table holds the plain fields of the service's card, and each secret field is a file inDRUKS_SECRETS_DIR. At startup, before HTTP traffic and DBOS recovery, the card validates its entry and Druks stores it in the card's encrypted vault row. Existing consumers keep their vault reads and row IDs.The API refuses edits and disconnects for a managed card. The Services page names the manager from the top-level
managed_bykey and disables those controls. A restart applies a changed entry. When the table is removed, the card keeps its credentials and can be changed on the Services page again.The table is for a platform that writes
druks.tomlitself: the installer refuses it. WAHA is the first use. The mechanism names no service: any registered service slug works.docs/configuration.mddocuments the table.