Concepts
Customizer Extension Points
The project follows Spring Boot's functional-bean idiom: auto-config consumes ObjectProvider<XCustomizer> and applies all customizers in order. Consumers define a @Bean implementing the interface — no auto-config editing needed.
Three levels exist:
ClientCustomizer— applied to theClientbean after it is created (ClientAutoConfiguration/MultiProviderAutoConfiguration). Use for hooks or client-level tweaks.OpenFeatureAPICustomizer— applied to the globalOpenFeatureAPIsingleton (OpenFeatureAPIAutoConfiguration). The built-in logging customizer and the features/security-integration hook both use this. Consumers can add hooks, event handlers, etc.- Provider customizers (e.g.
UnleashCustomizer) — applied to the provider's config builder inside the provider auto-config. Use for settings not covered byspring.openfeature.<provider>.*properties (entities/configuration-properties).
All customizers are Ordered-aware (orderedStream()), so consumers can control application order.