Features
Multi-Provider Mode
The multiprovider starter lets one app combine several flag backends behind a single Client.
MultiProviderAutoConfiguration (activates when dev.openfeature.contrib.providers.multiprovider.MultiProvider is on the classpath):
- Exposes a
Strategybean — defaultFirstMatchStrategy, replaceable by the consumer. - Collects all
FeatureProviderbeans (from however many provider starters are present) into aMultiProviderbean. - Exposes the
Clientitself viamultiClient(...), after running allClientCustomizers.
Interaction with the default flow: ClientAutoConfiguration is guarded by @ConditionalOnMissingBean(name = "multiProvider"), so in multi-provider mode the generic client bean steps aside and this module owns it. All provider auto-configs are also ordered @AutoConfigureBefore this one. See flows/startup-flow and risks/fragile-behavior for why this bean name matters.