Declarative Configuration specifies the required state of a subject without prescribing the sequence of operations used to establish that state.
The configured subject may include:
Declarative Configuration may specify:
A tool or process evaluates the declared state and determines the operations required to establish or preserve that state.
Declarative Configuration differs from procedural configuration:
Declarative Configuration does not prohibit an implementation from using an execution sequence. The distinction concerns whether the configuration itself prescribes that sequence.
Declarative Configuration may form part of Infrastructure as Code when represented as a machine-readable Artifact.
configuration that specifies the required state of a subject without prescribing the sequence of operations used to establish that state
Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
Declarative Configuration may be:
A declarative representation does not by itself establish that the configuration is:
Separate requirements govern those determinations.
The term does not require a particular configuration language, schema, file format, deployment tool, cloud provider, operating system, or implementation technology.
A Declarative Configuration specifies that an Infrastructure Environment contains three compute resources, persistent storage, defined network relationships, identity services, logging, and monitoring. The configuration does not prescribe the sequence in which the deployment system creates those resources.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.