Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:t:target_environment [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:t:target_environment [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Target Environment ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Target Environment is the environment selected to receive, execute, host, verify, or operate a build artifact, software release, machine image, infrastructure baseline, or deployment. | ||
| + | |||
| + | The Target Environment establishes the applicable technical, security, compliance, connectivity, | ||
| + | |||
| + | A Target Environment may be a development, | ||
| + | |||
| + | The Target Environment influences image selection, infrastructure configuration, | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Generalized from systems engineering, | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Target Environment identifies the destination of a defined build or deployment activity. The same environment may serve as the Target Environment for one activity and as a source or build environment for another activity. | ||
| + | |||
| + | A Target Environment may contain one or more [[public: | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A deployment description identifies an air-gapped enclave as the Target Environment for a hardened Kubernetes platform. Crucible selects the required machine images, infrastructure definitions, | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||