Plan configured secrets bootstrap implementation
This commit is contained in:
@@ -191,36 +191,19 @@ main-root options. This covers the requested deployment pattern and reuses the
|
||||
native secret-file checks. Caller-supplied filesystem support is a possible
|
||||
later extension requiring decisions about file-type and symlink capabilities.
|
||||
|
||||
## Work needed
|
||||
## Target integration
|
||||
|
||||
- Add `config.secrets_dir` and `config.secrets_overwrite` to the main-document
|
||||
control grammar and consume them during ordinary loading without triggering
|
||||
bootstrap. Retain source-local positions for diagnostics.
|
||||
- Factor main-file selection and capture for use by the companion helper and
|
||||
normal acquisition. Add a prepared-source handoff with retained main contents,
|
||||
identity, context, and ownership. Supply the preparation filesystem context and
|
||||
optional Go overwrite choice as described above. Preserve per-load accounting,
|
||||
diagnose incompatible later contexts, and implement the failure/return contract.
|
||||
- Preserve the current direct-directory signature and add a separately named
|
||||
options-bearing helper. Reuse directory bootstrap from all three entry points,
|
||||
with matching reports and failures. Finalize public names during implementation.
|
||||
- Verify discovery from a different working directory, canonical main paths,
|
||||
optional search exhaustion, declaration scope, default and explicit
|
||||
overwrite choices, Go-over-YAML precedence, and all helper interfaces. Include
|
||||
assignment of the unchanged helper to its existing function type.
|
||||
Cover empty values, dot entries, read failures before writes, and partial
|
||||
write failures. Verify bootstrap includes entries unused by typed fields and
|
||||
that later load failures preserve bootstrap effects.
|
||||
- Verify error types, empty and partial reports, and unusable prepared sources on
|
||||
failure. Cover absent-main success and failed later loads without rollback.
|
||||
- Verify prepared-source reuse after main-file changes and discovery changes,
|
||||
live later imports and environment lookup, equivalent and incompatible later
|
||||
contexts, handle cleanup, normal loading without
|
||||
environment writes, and agreement with selected-file provenance, placement,
|
||||
relative imports, and main-relative companions. Use disposable credential
|
||||
values and deterministic failure seams in line with the
|
||||
[testing policy](../policy/testing.md).
|
||||
- Document the startup workflow and add a consumer example. Implement the
|
||||
ownership decision in ADR 0023 and update the canonical configuration contract,
|
||||
public source documentation, and affected component documentation when the
|
||||
behavior lands. Retire the roadmap reference in architecture policy at that time.
|
||||
Main-file selection and bounded capture are shared with normal acquisition.
|
||||
The prepared source carries the main contents, identity, and context through
|
||||
ordinary and layered loading with normal placement, accounting, and source
|
||||
records. Directory bootstrap has one implementation behind the existing helper,
|
||||
the options-bearing helper, and the configured companion.
|
||||
|
||||
Canonical configuration and public source documentation describe the two-call
|
||||
startup flow, capture lifetime, and overwrite policy. Consumer examples and
|
||||
behavioral tests cover discovery, prepared-source reuse, relative inputs,
|
||||
failure reporting, environment effects, and ordinary loading's boundaries under
|
||||
the [testing policy](../policy/testing.md).
|
||||
|
||||
The [implementation plan](implementation.md) owns the selected API names,
|
||||
execution stages, and validation work needed to reach this target.
|
||||
|
||||
Reference in New Issue
Block a user