Configuration Source
Discussion
A Configuration Source provides one or more Configuration Values used in a Node Configuration.
Configuration Sources include controlled configuration files, environment settings, command-line arguments, configuration services, secret stores, databases, Deployment Descriptions, inherited configurations, approved defaults, and authorised human input.
The Configuration Source identifies the origin of a Configuration Value. Source authority identifies the person, organisation, policy, process, or other authority responsible for approving or controlling the source.
Recording the Configuration Source supports Provenance, Reproducibility, validation, and Traceability.
Definition
identified origin from which a Configuration Value is obtained
Source
DIDO Solutions project definition.
Note
A Configuration Source includes sufficient identifying information to distinguish it from other sources and revisions.
The identifying information includes the source type, owner, authority, version, location, applicable period, protection requirements, and method used to verify its Integrity.
Where multiple Configuration Sources provide values for the same Configuration Parameter, an explicit precedence rule determines which value applies.
Example
A version-controlled configuration file containing the approved DDS domain identifier and Quality of Service profile constitutes a Configuration Source.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.