Repository navigation
Take the deployment paths from instrument.toml and derive each instance's config - #5
Merged
Merged
Conversation
mikelangmayr
requested review from
Kupaianaha,
prkrtg and
scizen9
as code owners
October 14, 2026 18:21
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
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.
[paths]ininstrument.tomlsetsetc,venv,repoandlogs, each resolved as<PREFIX>_*_DIR, then the file, then the name-derived default, so a non-standard layout is recorded in the instrument's repository rather than in each operator's environment<etc>/<instance>.yamlinstead of being declared per instance, which is what made the layout only half-configurable: movingetcleft the configs behinddeploy,status --verbose,doctorand the secret scan all use the derived path;doctorwarns when a deployed instance file still sets the now-unread variableinstaller.log_diranddoctor.LOG_DIR_TEMPLATEeach derived/var/log/<name>separately; both now usepaths.logsinstrument.toml.example, with a test that it still loads so it cannot drift from the schema