public:99_annexes:annex-b-terms-and-definitions:d:dependency

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:d:dependency [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:d:dependency [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Dependency ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Dependency is an entity, resource, service, condition, or capability that another entity relies on to perform a defined function, complete a process, or satisfy a requirement.
 +
 +A Dependency may include software, packages, libraries, installation media, repositories, machine images, container images, provider plugins, infrastructure services, tools, credentials, configuration, information, or external operational capabilities.
 +
 +Dependencies may apply during build, deployment, execution, assessment, maintenance, or recovery. The applicable lifecycle context determines when and why the dependency is required.
 +
 +Within Crucible, dependency management identifies, captures, records, transfers, and reconstructs the inputs required to build and maintain environments in connected and disconnected operating contexts.
 +
 +===== Definition =====
 +
 +//entity, resource, service, condition, or capability on which another entity relies to perform a defined function, complete a process, or satisfy a requirement//
 +
 +===== Source =====
 +
 +Generalized from systems engineering, software engineering, dependency management, infrastructure automation, and supply-chain usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +A Dependency is not limited to software libraries or packages. It may be technical, informational, operational, organizational, or environmental.
 +
 +A Dependency may itself rely on other Dependencies, forming a dependency relationship or dependency chain that requires separate identification and control.
 +
 +===== Example =====
 +
 +A Crucible Image Build depends on a [[public:99_annexes:annex-b-terms-and-definitions:r:rhel]] 9 installation medium, package repositories, Packer, Ansible collections, compliance content, and the tools required to create and inspect the resulting Machine Image.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>