7.6 Rebuild and Deploy [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 7.6 Rebuild and Deploy ======

[[dido:02-crusible:07-disconnected-and-air-gapped-operations:start|Go to 7. Disconnected and Air-Gapped Operations]]

Within the destination [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]] or [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]], [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] uses the imported content and populated [[dido:99_annexes:annex-b-terms-and-definitions:o:offline_repository|Offline Repositories]] to construct required Images and deploy the intended environment.

The destination-side lifecycle uses locally available inputs rather than depending on direct access to connected repositories, registries, provider services, or other unavailable external resources.

===== Prepare the Destination-Side Inputs =====

Crucible identifies the controlled inputs required for the destination-side construction and deployment activities.

The inputs can include:

  * Imported application content
  * Selected Baselines
  * Image Layers
  * Infrastructure Baselines
  * Base Images
  * Software packages
  * Build tools
  * Runtime libraries
  * Configuration definitions
  * Compliance content
  * Provider tools and plugins
  * Direct and transitive Dependencies
  * Deployment parameters
  * Provider-specific parameters

The applicable lifecycle definition determines which inputs the activity requires.

Crucible obtains those inputs from the imported Transfer Bundle, populated Offline Repositories, approved destination repositories, or other authorized resources available within the destination environment.

===== Resolve Dependencies Locally =====

Destination-side tools resolve required Dependencies from the populated Offline Repositories.

Local dependency resolution avoids reliance on an unavailable connected source.

The resolution activity can confirm:

  * The required Dependency is available
  * The selected version or revision is available
  * Direct and transitive Dependencies are resolvable
  * Required repository metadata is available
  * Recorded integrity information matches the local content
  * The Dependency is available to the applicable construction or deployment tool

Crucible does not silently substitute another Dependency version when the selected version is unavailable.

A missing or unresolved Dependency can prevent the applicable construction or deployment activity from completing.

===== Rebuild Images =====

When the destination activity requires a Machine Image or Container Image, Crucible constructs the Image from the locally available controlled inputs.

The reconstruction activity can include:

  - Select the applicable Image definition
  - Resolve required Dependencies from Offline Repositories
  - Apply the selected Image Layers
  - Apply application and configuration content
  - Execute the applicable build process
  - Produce the resulting Image
  - Assign the Image identifier and revision
  - Record the Image content digest
  - Sign or verify the Image when required by the applicable workflow
  - Record the construction result

The reconstructed Image remains associated with the Baselines, Dependencies, parameters, and other controlled inputs used to produce it.

A destination-side reconstruction does not require the resulting Image to have the same provider-specific representation as an Image constructed in another environment. The applicable requirements and Acceptance Criteria determine whether the reconstructed result is acceptable.

===== Prepare the Deployment =====

Crucible prepares the locally available inputs required to realize the destination environment.

The deployment inputs can include:

  * The applicable Infrastructure Baseline
  * Reconstructed or imported Machine Images
  * Reconstructed or imported Container Images
  * Application artifacts
  * Configuration definitions
  * Network definitions
  * Storage definitions
  * Security configuration
  * Locally available Dependencies
  * Credential references
  * Deployment parameters
  * Provider-specific parameters

Each input retains its identity and revision so Crucible can relate the deployed result to the content used to create it.

===== Select the Destination Deployment Target =====

Crucible identifies an authorized Deployment Target within the destination environment.

The selected target must provide the resources and interfaces required by the applicable deployment definition.

A destination Deployment Target can include:

  * Virtualized infrastructure
  * Physical infrastructure
  * Container infrastructure
  * Private cloud infrastructure
  * Local platform services
  * Another supported infrastructure environment available within the destination Security Domain

The applicable Provider Implementation resolves provider-independent deployment intent into the operations and parameters required by the selected destination platform.

===== Deploy the Environment =====

Crucible performs the operations required to realize the intended environment on the selected destination Deployment Target.

The deployment can include:

  - Verify the required deployment inputs
  - Verify locally available Dependencies
  - Prepare the Deployment Target
  - Create or configure infrastructure resources
  - Create network and storage resources
  - Instantiate Machine Images or Container Images
  - Apply configuration
  - Deploy application workloads
  - Apply security configuration
  - Execute required post-deployment activities
  - Record the result of each operation

The applicable Infrastructure Baseline and deployment definition determine which operations apply and their required order.

===== Operate Without Connected Resources =====

The reconstruction and deployment activities use resources available within the destination operational boundary.

The activities do not depend on direct access to:

  * External source repositories
  * External package repositories
  * External Image registries
  * Connected build services
  * Connected assessment services
  * Unavailable provider services
  * Other resources outside the destination boundary

If a required resource is not available locally, Crucible records the unresolved condition rather than substituting an unidentified resource or bypassing the applicable boundary controls.

===== Handle Construction and Deployment Failures =====

Crucible records a failure that prevents successful reconstruction or deployment.

A failure record can identify:

  * The failed activity
  * The affected Image or Deployment Target
  * The controlled inputs supplied
  * The missing or unresolved Dependency
  * The observed failure
  * The operations completed before the failure
  * The resources created or changed
  * The resulting state

The applicable workflow determines whether the failure requires correction, production of another Transfer Bundle, additional repository population, reconstruction, redeployment, rollback, or another authorized activity.

===== Rebuild and Deployment Result =====

The result identifies:

  * The destination environment
  * The controlled inputs used
  * The Offline Repositories used
  * The Dependencies resolved
  * Each constructed Image
  * Each Image identifier and revision
  * The selected Deployment Target
  * The Infrastructure Baseline and revision
  * The Provider Implementation
  * The deployment parameters
  * The deployment operations performed
  * The status of each operation
  * The resources created or changed
  * The resulting deployment status
  * Any missing Dependency, failure, or unresolved condition

The resulting deployment can undergo the applicable deployment validation and compliance assessment activities within the destination environment.

===== Requirements Addressed =====

^ Requirement ^ Statement ^
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-001]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-001#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-002]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-002#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-001]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-001#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-002]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-002#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-003]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-003#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-004]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-004#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-005]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-005#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-10-dependency-capture-and-offline-transfer:fr-depc-004]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-10-dependency-capture-and-offline-transfer:fr-depc-004#Statement&noheader&nofooter&noeditbtn}} |

The linked leaf requirement pages remain the canonical sources.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>