Extending an existing actuator endpoint that already has spring built-in extension

[mipo256]

We need to write our own extension for the EnvironmentEndpoint to enrich the response with some additional metadata. But the EnvironmenEndpoint already has an extension - EnvironmentEndpointWebExtension, which we also need, we cannot throw it away.

As stated in this issue, it is impossible to have multiple extensions for a single endpoint.

I do not really know the best solution here, but based on the aforementioned issue, it seems that the problem is quite common: we want to extend the actuator endpoint, and this endpoint already has a spring extension, so we have this dillema.

So, maybe it will be possible can separate somehow built-in Spring extensions from the extensions of end-users, or even design a solution that would allow us to have multiple extensions for a single endpoint (if feasible), I'm not really sure what is the best approach. But the problem is there.

[wilkinsona]

Have you tried declaring a bean that is a sub-class of EnvironmentEndpointWebExtension? That should cause the auto-configuration of Boot's extension to back off and allow you to add to the extension.