Record explicit configured secrets bootstrap and refine its roadmap
This commit is contained in:
@@ -405,9 +405,14 @@ Secret values enter configuration through typed environment-name references;
|
||||
literal credentials are not a supported configuration convention. Only an explicit
|
||||
accessor exposes a resolved credential to application code. Credential bytes must
|
||||
never enter composition trees, history, or inspection. General environment-variable
|
||||
configuration overlays are an explicit non-goal. Bootstrap must preserve already
|
||||
set variables, including empty ones, and report blocked files without contents.
|
||||
See [ADR 0004](../adr/0004-secret-references-and-explicit-bootstrap.md).
|
||||
configuration overlays are an explicit non-goal. Bootstrap preserves already
|
||||
set variables by default, including empty ones, and reports blocked files without
|
||||
contents. [ADR 0023](../adr/0023-explicit-configured-secrets-bootstrap.md) permits
|
||||
explicit overwrite and main-document-directed bootstrap as a separate startup
|
||||
operation. Its implementation is tracked in the
|
||||
[secrets-directory roadmap](../roadmap/secrets-directory.md); the
|
||||
[configuration contract](../config.md#explicit-secrets-directory-bootstrap)
|
||||
owns current behavior.
|
||||
|
||||
Secrets must be considered throughout error handling and inspection. Library
|
||||
renderers must apply secret classification, and parser errors must not be
|
||||
|
||||
Reference in New Issue
Block a user