public:99_annexes:annex-b-terms-and-definitions:p:provider_mirror

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:p:provider_mirror [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:p:provider_mirror [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Provider Mirror ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Provider Mirror is a controlled local or internal copy of infrastructure-provider software packages and associated metadata used by infrastructure automation tooling without direct access to the original distribution source.
 +
 +The mirror may contain provider binaries, versions, platform-specific packages, integrity values, signatures, indexes, and source information.
 +
 +A Provider Mirror supports deterministic and disconnected initialization of [[public:99_annexes:annex-b-terms-and-definitions:i:iac|Infrastructure as Code (IaC)]] tooling.
 +
 +Within Crucible, a Provider Mirror may be included in a [[public:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle|Transfer Bundle]] and used during [[public:99_annexes:annex-b-terms-and-definitions:p:platform_initialization|Platform Initialization]] in a disconnected enclave.
 +
 +===== Definition =====
 +
 +//controlled local or internal copy of infrastructure-provider software packages and associated metadata used without direct access to the original distribution source//
 +
 +===== Source =====
 +
 +Generalized from Infrastructure as Code tooling, package mirroring, plugin distribution, disconnected operations, and software supply-chain management and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +A Provider Mirror stores provider software packages. It differs from a [[public:99_annexes:annex-b-terms-and-definitions:p:provider_registry|Provider Registry]], which identifies and resolves Provider Plugins within an application architecture.
 +
 +A Provider Mirror should preserve the exact versions, integrity values, and platform compatibility information required by the infrastructure tooling.
 +
 +===== Example =====
 +
 +A connected environment downloads the required OpenTofu provider packages for Linux on x86-64 and AArch64, records their integrity values, and transfers them into a Provider Mirror inside an air-gapped enclave.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>