Provider Mirror

Go up to Terms and Definitions

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 Infrastructure as Code (IaC) tooling.

Within Crucible, a Provider Mirror may be included in a Transfer Bundle and used during Platform Initialization in a disconnected enclave.

controlled local or internal copy of infrastructure-provider software packages and associated metadata used without direct access to the original distribution 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.

A Provider Mirror stores provider software packages. It differs from a 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.

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.