| Both sides previous revision Previous revision | |
| public:99_annexes:annex-b-terms-and-definitions:p:provider_registry [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:p:provider_registry to public:99_annexes:annex-b-terms-and-definitions:p:provider_registry nick_dido | public:99_annexes:annex-b-terms-and-definitions:p:provider_registry [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| ====== Provider Registry ====== | ====== Provider Registry ====== |
| |
| [[private:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] | [[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] |
| |
| ===== Discussion ===== | ===== Discussion ===== |
| |
| A Provider Registry records and resolves the available [[private:99_annexes:annex-b-terms-and-definitions:p:provider_plugin|Provider Plugins]], their identities, supported contract versions, capabilities, compatibility information, and loading mechanisms. | A Provider Registry records and resolves the available [[public:99_annexes:annex-b-terms-and-definitions:p:provider_plugin|Provider Plugins]], their identities, supported contract versions, capabilities, compatibility information, and loading mechanisms. |
| |
| The registry provides a controlled discovery point through which core software locates and selects a plugin for a specified [[private:99_annexes:annex-b-terms-and-definitions:p:provider|Provider]] or deployment requirement. | The registry provides a controlled discovery point through which core software locates and selects a plugin for a specified [[public:99_annexes:annex-b-terms-and-definitions:p:provider|Provider]] or deployment requirement. |
| |
| A Provider Registry may validate plugin metadata, reject incompatible implementations, expose supported capabilities, and enforce a single approved loading path. | A Provider Registry may validate plugin metadata, reject incompatible implementations, expose supported capabilities, and enforce a single approved loading path. |
| |
| Within the Crucible architecture, the Provider Registry helps preserve the cloud-agnostic boundary by ensuring that provider-specific implementations enter the system through the defined [[private:99_annexes:annex-b-terms-and-definitions:p:provider_contract|Provider Contract]]. | Within the Crucible architecture, the Provider Registry helps preserve the cloud-agnostic boundary by ensuring that provider-specific implementations enter the system through the defined [[public:99_annexes:annex-b-terms-and-definitions:p:provider_contract|Provider Contract]]. |
| |
| ===== Definition ===== | ===== Definition ===== |
| |
| //registry that records and resolves available [[private:99_annexes:annex-b-terms-and-definitions:p:provider_plugin|provider plugins]], their identities, supported contract versions, capabilities, compatibility information, and loading mechanisms// | //registry that records and resolves available [[public:99_annexes:annex-b-terms-and-definitions:p:provider_plugin|provider plugins]], their identities, supported contract versions, capabilities, compatibility information, and loading mechanisms// |
| |
| ===== Source ===== | ===== Source ===== |