FR-CFG-001 — Declarative Infrastructure Configuration

Go to Crucible Configuration Management Requirements

Crucible SHALL define infrastructure through Declarative Configuration.

This requirement derives from:

• Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, Configuration Management, FR-CFG-001

The Original Requirement states:

The system SHALL define infrastructure through declarative configuration.[C1]

FR-CFG-001 replaces The system with the defined system name Crucible.

No other substantive normalization is required.

Declarative Configuration defines the required infrastructure without requiring the configuration to prescribe the procedural steps used to realize it.

This separation allows infrastructure definitions to remain independent of the implementation tools and execution mechanisms used to create or modify the infrastructure.

This requirement applies to:

• Crucible
• Infrastructure
• Declarative Configuration

Verification confirms that:

1. Crucible accepts or produces a Declarative Configuration that defines infrastructure
2. The tested Declarative Configuration identifies the infrastructure defined by the configuration
3. The tested Declarative Configuration expresses the required infrastructure without depending on a prescribed procedural execution sequence

The following pages reference this requirement:

Phase 1 and subsequent phases

Assess whether the current Crucible implementation defines infrastructure through Declarative Configuration.

Review and approve FR-CFG-001 as a leaf requirement.

Determine the minimum information required for a Declarative Configuration to define infrastructure.

This requirement page retains the stable requirement identifier FR-CFG-001.

This page is a leaf requirement page and omits a trailing :start from its namespace.

The Statement preserves the approved source intent and changes only the actor from The system to the defined system name Crucible.

Do not add desired-state representation, Infrastructure Environment identification, execution-sequence constraints, validation, approval, versioning, deployment, or history obligations to the Statement unless the controlling requirement changes through an approved requirements process.

To reference this requirement Statement from another wiki page, insert:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:fr-cfg-001#Statement&noheader&nofooter&noeditbtn}}