FR-CFG-002 — Infrastructure as Code

Go to Crucible Configuration Management Requirements

Crucible SHALL represent each Infrastructure Configuration as a machine-readable, version-controlled Artifact.

The system SHALL support Infrastructure-as-Code methodologies.

Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, Configuration Management, FR-CFG-002.

The source statement expresses the approved functional intent but does not provide all information required for deterministic verification.

The following Specification Discipline and Authoring findings apply:

• The system does not use the defined system name
• Support is a weak verb that does not identify the behavior Crucible performs
• Infrastructure-as-Code does not identify the infrastructure information represented as code
• Methodologies does not identify the required representation or observable result
• The source statement does not identify whether the infrastructure representation must be machine-readable
• The source statement does not identify whether the representation must be controlled through Version Control
• The source statement does not distinguish artifact representation from revision-history preservation

The normalized Statement:

• Replaces The system with the defined system name
• Replaces support with the direct behavior represent
• Identifies the Infrastructure Configuration as the represented information
• Identifies a machine-readable Artifact as the required representation
• Requires the Artifact to remain under Version Control

This requirement governs the representation and control of the Infrastructure Configuration Artifact. FR-CFG-005 separately governs preservation of configuration revisions and the relationships among successive revisions.

Infrastructure as Code applies software configuration management practices to infrastructure definitions.

An Infrastructure Configuration that exists only as an informal document, manually executed procedure, or untracked script cannot serve as a consistently processable and controlled infrastructure definition.

A machine-readable representation allows an authorized tool or workflow to process the Infrastructure Configuration without manual transcription.

Version Control places the Infrastructure Configuration Artifact under controlled revision management.

The machine-readable, version-controlled representation provides a foundation for separately defined behaviors such as:

• Configuration reuse
• Configuration inheritance
• Configuration revision preservation
• Configuration comparison
• Infrastructure deployment
• Environment reconstruction

This representation contributes to:

• Consistent automated processing
• Controlled configuration change
• Configuration reuse
• Reproducibility
• Provenance
• Traceability

This requirement applies to:

• Crucible
• Infrastructure as Code
• Infrastructure Configurations
• Artifacts
• Machine-readable representations
• Version Control

1. Verification SHALL confirm that each tested Infrastructure Configuration exists as an identifiable Artifact
2. Verification SHALL confirm that each tested Infrastructure Configuration Artifact uses a machine-readable representation
3. Verification SHALL confirm that an authorized tool can parse the machine-readable representation without manual transcription
4. Verification SHALL confirm that each tested Infrastructure Configuration Artifact is maintained under the applicable Version Control system
5. Verification SHALL confirm that the Version Control system assigns an identifiable revision to the tested Infrastructure Configuration Artifact
6. Verification SHALL confirm that an authorized user or process can retrieve the identified revision

Verification may include:

• Artifact inspection
• Machine-readable format inspection
• Automated parsing tests
• Version Control repository inspection
• Revision identification tests
• Revision retrieval tests

The verification record SHALL identify:

1. The tested Infrastructure Configuration
2. The corresponding Artifact
3. The machine-readable representation
4. The tool used to parse the representation
5. The parsing result
6. The applicable Version Control system
7. The tested revision identifier
8. The revision retrieval result
9. The observed results
10. The generated Evidence

This requirement refines:

• MO-001 — Repeatable, Compliant, and Secure Infrastructure Environments
• MO-002 — Reduced Platform Deployment Timelines
• MO-003 — Platform Independent Deployment
• MO-005 — Reusable and Version-Controlled Infrastructure
• MO-006 — Infrastructure Lifecycle Management

This requirement operates within the conditions established by:

• OR-001 — Operational Roles
• OR-002 — Deployment Environments
• OR-003 — Classified and Unclassified Environments
• OR-004 — Concurrent Environment Management
• OR-005 — Distributed Environment Management

This requirement also relates to:

• 5. Descriptions, Composition, and Baselines
• 7. Infrastructure and Deployment
• 10. Reproducibility, Provenance, and Traceability

The wiki Backlinks function provides the current list of pages that reference FR-CFG-002.

Incoming traceability should be derived dynamically from backlinks rather than maintained as a duplicate manual list.

Backlinks identify incoming references but do not define the semantics of each relationship. Referencing pages should identify whether the relationship represents realization, refinement, verification, dependency, or another defined traceability relationship.

The Crucible Concept of Operations describes Phase 1 as a command-line utility invoked through CI/CD Pipeline steps.

The Phase 1 workflow uses machine-readable, version-controlled Infrastructure Configuration Artifacts as controlled inputs for activities such as:

• Selecting an identified configuration revision
• Composing selected Baselines
• Building Machine Images
• Preparing deployment inputs
• Performing Infrastructure Deployment

The machine-readable representation allows automated processing. Version Control provides controlled identification and retrieval of the Artifact revision used by the workflow.

Phase 1 and subsequent phases

Not Assessed

Implementation status requires verification that Crucible represents each Infrastructure Configuration as a machine-readable, version-controlled Artifact.

Draft

The source System Requirements Specification identifies Version 1.1 as a draft.

This requirement page should retain the stable requirement identifier FR-CFG-002.

Changes to the Statement SHALL preserve the approved intent of the source requirement.

Material changes should receive review and should update the related outbound traceability, verification criteria, and source records.

The Source Statement should preserve the original wording from the controlling System Requirements Specification.

Verification criteria should test only the Artifact representation, machine readability, and Version Control behavior defined by the Statement.

Revision-content preservation and relationships among successive revisions belong to FR-CFG-005 and should not be duplicated as normative behavior on this page.

Incoming traceability should use the wiki Backlinks function rather than a manually maintained list.

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-002#Statement&noheader&nofooter&noeditbtn}}

Do not rename this page after an external citation unless a redirect or move plan is in place.