FR-MC-002 — Provider-Specific Extensions

Go to Crucible Multi-Cloud Management Requirements

Statement

Crucible SHALL provide provider-specific extensions through Provider Plugins.

Derived From

This requirement derives from:

Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-MC-002The Original Requirement states:

The system shall support provider-specific extensions through plugins.[C1]

FR-MC-002:

Replaces The system with the defined system name CrucibleChanges shall to the established uppercase normative form SHALLReplaces the weak verb support with provideUses the defined Provider Plugin conceptPreserves plugins as the source-required extension mechanismNo other substantive normalization is required.

Rationale

Providers expose capabilities, interfaces, parameters, and lifecycle operations that differ from those exposed by other Providers.

A Provider Plugin allows Crucible to provide provider-specific behavior without incorporating that behavior directly into provider-independent Crucible components.

Provider-specific extensions can address:

Provider resource typesProvider interfacesProvider authenticationProvider regionsProvider networkingProvider storageProvider machine typesProvider-managed servicesProvider-specific deployment operationsProvider-specific validationProvider-specific error handlingThis requirement establishes Provider Plugins as the extension mechanism without prescribing:

Plugin discoveryPlugin installationPlugin loadingPlugin activationA Provider ContractVersion compatibilityPlugin isolationPlugin signingPlugin substitutionPlugin removalA programming language or packaging formatSeparate requirements, architecture specifications, or interface definitions govern those subjects.

Applies To

This requirement applies to:

Provider-specific extensionsProvider PluginsProvider-specific behavior

Verification

Verification confirms that:

Provider-specific behavior is selected for testingThe tested provider-specific behavior is provided through a Provider PluginCrucible uses the Provider Plugin to provide the tested provider-specific behaviorThe observed behavior demonstrates a provider-specific extension supplied through the Provider Plugin

Referenced By

The following pages reference this requirement:

Implementation Status

Implemented and Verified

Requirement Status

Issues

Notes for Editors

This requirement page retains the stable requirement identifier FR-MC-002.

This page is a leaf requirement page and omits a trailing :start from its namespace.

The Statement preserves the source-required use of plugins for provider-specific extensions.

Do not generalize the extension mechanism beyond Provider Plugins without a corresponding change to the controlling requirement.

Do not add Provider Plugin discovery, installation, loading, activation, Provider Contract conformance, version compatibility, isolation, signing, substitution, or removal obligations unless the controlling requirement changes through an approved requirements process.

To reference this requirement Statement from another wiki page, insert:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-002#Statement&noheader&nofooter&noeditbtn}}

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.