Adopt native configuration search precedence in the roadmap
This commit is contained in:
@@ -142,11 +142,26 @@ domain semantics applied to the final configuration.
|
||||
Replace manual acquisition/probing with ConfigKit source descriptions. Explicit
|
||||
`--config` and, when no CLI selection exists, `NOTARIUS_CONFIG` select exclusive
|
||||
`File` sources: a missing selected file fails instead of searching elsewhere.
|
||||
For default discovery use `SearchConfig` with `UnixSystemDirectories()`.
|
||||
The native preset fits Notarius's sysadmin-focused deployment and includes the
|
||||
existing installed location among its conventional candidates. Document its
|
||||
candidate names/order and native first-selected-file failure behavior. User,
|
||||
home, and working-directory presets are not enabled by this choice.
|
||||
For default discovery use `SearchConfig` with `Searches` composing these native
|
||||
presets in order:
|
||||
|
||||
1. `WorkingDirectory()`;
|
||||
2. `UserConfigDirectory()`; and
|
||||
3. `UnixSystemDirectories()`.
|
||||
|
||||
Together with the explicit selections above, precedence is `--config`, then
|
||||
`NOTARIUS_CONFIG`, then working-directory, user-configuration, and system searches.
|
||||
Retain each preset's native filename groups and ordering. In particular, the
|
||||
working-directory preset selects `notarius.yml`, then `notarius.yaml`, rather
|
||||
than generic `config.yml`. The separate `HomeDirectory()` preset is not enabled.
|
||||
|
||||
Discovery selects one main file; it does not merge files from all search
|
||||
locations. Missing candidates advance the search under ConfigKit's rules. Access
|
||||
errors and failures loading a selected file are terminal rather than reasons to
|
||||
try a lower-priority configuration. Document working-directory-dependent
|
||||
selection and recommend explicit `--config` for services and subprocess callers
|
||||
that want a fixed selection.
|
||||
|
||||
Use a required search for commands that require a configuration file, preserving
|
||||
their need for a selected configuration. This does not impose requiredness on
|
||||
all imports or on separate defaults-only programmatic loads.
|
||||
@@ -268,6 +283,6 @@ dependencies when no longer used. It will also update the relevant tests,
|
||||
inspection/checkpoint integration, documentation, and attribution for the final
|
||||
selected graph. That later work does not gate completion of this v1.2.0 scope.
|
||||
|
||||
The dependency approach, Unix-system discovery preset, and application step
|
||||
The dependency approach, ordered native discovery presets, and application step
|
||||
identity registration are approved decisions. No significant open decisions
|
||||
remain for this feature roadmap.
|
||||
|
||||
Reference in New Issue
Block a user