public:99_annexes:annex-b-terms-and-definitions:t:teardown

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:t:teardown [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:t:teardown [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Teardown ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +Teardown is the controlled process of deactivating, detaching, removing, or releasing resources and services created or managed for a defined [[public:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]].
 +
 +The process may stop services, remove compute instances, release networking and storage resources, revoke temporary credentials, remove provider registrations, preserve required records, and verify that no unintended resources remain.
 +
 +Teardown forms part of lifecycle management and may apply to development, test, staging, production, recovery, or temporary environments.
 +
 +Within Crucible, Teardown uses the deployment information and provider mechanisms associated with the selected [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] and [[public:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platform]].
 +
 +===== Definition =====
 +
 +//controlled process of deactivating, detaching, removing, or releasing resources and services created or managed for a defined deployment//
 +
 +===== Source =====
 +
 +Generalized from infrastructure automation, cloud-resource management, testing, deployment lifecycle, and configuration-management usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +Teardown does not necessarily delete every artifact associated with a Deployment. Applicable retention, audit, evidence, backup, and records-management requirements may require preservation of selected information.
 +
 +A successful Teardown verifies that the process removed or released the intended resources and did not leave unintended billable, accessible, or unmanaged resources.
 +
 +===== Example =====
 +
 +After completing a Kubernetes demonstration, Crucible removes the compute instances, load balancer, network resources, and temporary storage, then verifies that the provider reports no remaining billable deployment resources.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>