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

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_plugin [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:p:provider_plugin [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Provider Plugin ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Provider Plugin is a software component that implements a [[public:99_annexes:annex-b-terms-and-definitions:p:provider_contract|Provider Contract]] for a particular [[public:99_annexes:annex-b-terms-and-definitions:p:provider|Provider]] or class of Providers.
 +
 +The plugin translates provider-independent requests into provider-specific interfaces, commands, data structures, authentication mechanisms, and lifecycle operations.
 +
 +A Provider Plugin isolates provider-specific behavior from the core software. This separation allows the core to use a [[public:99_annexes:annex-b-terms-and-definitions:p:provider_abstraction|Provider Abstraction]] without importing or depending directly on provider-specific software development kits.
 +
 +Within the Crucible architecture, Provider Plugins may support image conversion, upload, signing, verification, promotion, description, infrastructure initialization, deployment, and teardown operations.
 +
 +===== Definition =====
 +
 +//software component that implements a [[public:99_annexes:annex-b-terms-and-definitions:p:provider_contract|provider contract]] for a particular [[public:99_annexes:annex-b-terms-and-definitions:p:provider|provider]] or class of providers//
 +
 +===== Source =====
 +
 +Generalized from plugin architecture, adapter, driver, provider-integration, and software-extension usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +A Provider Plugin is not the Provider itself. The plugin represents and invokes Provider capabilities through the applicable Provider Contract.
 +
 +A Provider Plugin may support only the capabilities available from its associated Provider. Unsupported capabilities remain explicit rather than being simulated within the core.
 +
 +===== Example =====
 +
 +An Oracle Cloud Infrastructure Provider Plugin translates Crucible image-upload and deployment requests into the interfaces and command-line operations required by Oracle Cloud Infrastructure.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>