Make methods in the CircuitBreaker that aren't publicly used private
There's specs added in !14417 (merged) listing the methods that could have been private, they're only used by the specs. So we need to double check that all cases are covered by the other CircuitBreaker specs, and then remove the ones directly testing the private API.
The following discussion from !14417 (merged) should be addressed:
-
@reprazent started a discussion: Clever! Let's add a ~"technical debt" issue for making the methods private and removing the related circuitbreaker specs. Making sure all cases are still covered.
/cc @nick.thomas