Closes #166, #105

Thanks! This is great!

If you would like we could merge this into our next minor release but we would have to rework the PR a bit to remove any kind of breaking changes to the APIs (changes to public method signatures).

If not we can wait till the next major to merge it (which would be in a few months).

Either way it would be nice to add some documentation about the reactive support.

Thanks for the feedback!

I prefer to merge this into your next minor release.

I have reworked the PR by adding additional constructors instead of changing the existing public method signatures.

The only place a public method signature (bean declaration) is changed is inside the ReactiveResilience4JAutoConfiguration class but this is done because we need to inject the ReactiveResilience4jBulkheadProvider bean into the ReactiveResilience4JCircuitBreakerFactory.

Should I create a separate bean method that includes the ReactiveResilience4jBulkheadProvider and mark the current one as @Primary?

Also, I agree to document that change.

No for the configuration class you can change that public method. Just mark the old constructors as @Deprecated

I annotated the old constructors with @Deprecated and extended the bulkhead-pattern-supporting documentation with an explanation of the newly added provider.

Just for clarification, when are you planning your next minor release?

Watch here for updates. We're doing some planning very soon and will add a date there.

After discussing scheduling with the team, the next minor will be in the June timeframe. You can keep an eye on our milestone dates for the most up to date information. That said we will likely merge this before the end of the month once we have a branch.