Sure, I will add it.
My question is not only for the actuator.
For example I want to add rest controller in my microservice which is not related to OData.
I want that this rest controller path will be <my-server-url>/api/<rest-controller-path>, and the OData request's path will be <my-server-url>/api/odata.
I saw that Olingo has a support for that ("org.apache.olingo.odata2.path.split" property).
(didn't find any documentation for that "split" for OData version 4)
Does Teiid have support for that?
We do not support "split" property, but I am sure Spring Boot will allow you to define two different contexts in a single app, why not use that? You can place odata impl in something like /odata, and your's in /api. If that needs any code changes I can help with that.
I did find an issue when a separate context being used for odata. I fixed that one for 1.0.2 release. Using this version you can define "server.context-path=/odata" property in the application.properties and have different odata endpoint. Then you can add the actuator spring boot starter for health stuff which will be at root.
I need to look into your /api endpoint next. If you want suggest code enhancements you are welcome, go ahead submit me patch and I will take look.
If you want to enable Actuator and also use root it is possible with Spring to open this on another port. See example here https://www.baeldung.com/spring-boot-actuators in Further Customization section.
Looked into this little bit today, I did not find any material that can allow two different contexts from single Spring Boot app, so that means I need to implement something like "split" functionality you mentioned before into Teiid. Go ahead and submit JIRA I can such functionality easily.
Actually I used another port in order to resolve this issue, but separating management and application ports is not best practice. I prefer to check "health" on the same port as my app requests.
Here is my configuration that resolved the issue: