Differences

This shows you the differences between two versions of the page.

--- public:99_annexes:annex-b-terms-and-definitions:d:declarative_configuration [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1
+++ public:99_annexes:annex-b-terms-and-definitions:d:declarative_configuration [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
+====== Declarative Configuration ======
+[[public:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]
+===== Discussion =====
+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:
+  * An [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]]
+  * An [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]]
+  * A platform
+  * A service
+  * A software component
+  * A network
+  * A computing resource
+  * A storage resource
+  * A security control
+Declarative Configuration may specify:
+  * Required resources
+  * Required configuration values
+  * Relationships among resources
+  * Required capabilities
+  * Applicable constraints
+  * Applicable [[public:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] references
+  * Applicable [[public:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]]
+  * Desired operational state
+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 specifies the required result
+  * Procedural configuration specifies the operations and sequence used to produce the result
+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 [[private:99_annexes:annex-b-terms-and-definitions:i:infrastructure_as_code|Infrastructure as Code]] when represented as a machine-readable [[public:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]].
+===== Definition =====
+//configuration that specifies the required state of a subject without prescribing the sequence of operations used to establish that state//
+===== Source =====
+Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+===== Note =====
+Declarative Configuration may be:
+  * Human-readable
+  * Machine-readable
+  * [[public:99_annexes:annex-b-terms-and-definitions:v:version_control|Version-controlled]]
+  * Reusable
+  * Parameterized
+  * Inherited
+  * Generated
+  * Composed from multiple controlled inputs
+A declarative representation does not by itself establish that the configuration is:
+  * Valid
+  * Approved
+  * Authorized for application
+  * Compatible with a target platform
+  * Successfully deployed
+  * Compliant with an applicable Baseline
+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.
+===== Example =====
+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.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>