====== Deployment Description ====== [[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] ===== Discussion ===== A Deployment Description is a machine-processable specification of the artifacts, resources, relationships, constraints, configuration, and lifecycle operations required for a [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]]. The description may identify the [[dido:99_annexes:annex-b-terms-and-definitions:t:target_environment|Target Environment]], [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platform]], [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]], infrastructure requirements, providers, dependencies, compliance expectations, provisioning content, verification activities, and teardown behavior. A Deployment Description states the intended deployment configuration and relationships without necessarily prescribing every provider-specific command used to realize them. Within Crucible, a [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Description]] may include or reference the information required to form a Deployment Description. ===== Definition ===== //machine-processable specification of the artifacts, resources, relationships, constraints, configuration, and lifecycle operations required for a [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment|deployment]]// ===== Source ===== Generalized from deployment automation, Infrastructure as Code, platform engineering, and configuration-management usage and specialized for the Crucible architecture and operational model. ===== Note ===== A Deployment Description differs from deployed state. The description specifies the intended deployment, while the deployed state records or represents the realized resources and configuration. A Deployment Description may remain provider-independent when provider-specific details are supplied through a [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_plugin|Provider Plugin]] or controlled profile. ===== Example ===== A Deployment Description identifies a verified [[dido:99_annexes:annex-b-terms-and-definitions:r:rhel]] 9 [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes]] image, three compute nodes, network requirements, storage, security controls, an Oracle Cloud Infrastructure provider, and post-deployment verification steps. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.