Add endpoint support for web-specific stack

In spring cloud there are numerous MvcEndpoints that took advantage of the ability of SpringMVC to add arbitrarily complex behaviors to the actuator such as:

• complex POST parameters (maps & objects)
• wrapping a servlet (/hystrix.stream), basically access to raw HttpServletRequest & HttpServletResponse

The benefit of having them in actuator is that they aren’t part of the main application and can be protected by actuator security.

If we move them to normal endpoints we would lose all of the benefits of actuator (global disabled, security, management port, etc…) that are users are used to.

Thoughts?

[philwebb]

@snicoll I missed that comment, rather than re-open this one I’ve raised #11703. We can certainly live with the extra meta-data in RC1.

[snicoll]

@philwebb the remark in my previous comment has not been fully addressed, specifically:

The caching feature would feel awkward: we provide a cache property automatically but it has no effect. That could be fixed by moving the cache configuration at management.endpoints.cache like we did for web path customization. The annotation processor would only generate an enabled flag and we should not be able to add any extra property to that namespace then. We need to figure out if we are ready to pay that price.

I’ve just tried with latest master and that property is generated. Is that deliberate or is it an oversight?