Permits Actuator endpoints to depend on HttpTracing #1680
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Actuator endpoints are queried to make the default skip pattern. There's an
edge case where actuator endpoints indirectly reference the still constructing
HttpTracing bean. Ex: an instrumented client could cause a cyclic dep.
This optimizes for the opposite: that custom actuator endpoints are not in
use. This allows configuration to be eagerly parsed, allowing any errors to
surface earlier. In the case there is a cyclic dep, this parsing becomes lazy,
deferring any errors creating the skip pattern.
Fixes #1679