This microservice, which I believe was initially generated by some IBM tool (Appsody?), has stuff in its pom.xml and elsewhere that refers to Cloud Foundry, Bluemix, and some IBM-proprietary monitoring. I don't have time at the moment to go find and remove all o this and test it all, but opening this as a reminder. The intention is that, like all of the other Stock Trader microservices, this one should be focused on Kubernetes, Jakarta, and MicroProfile and do things in industry-standard ways that would work on any cloud, rather than bundling in stuff like for agents for some IBM proprietary monitoring products. Need to do a review and cleanup of this microservice to bring it in line with the ones written by the Cloud Journey Optimization Team (this one was contributed by people on the Liberty team, which was appreciated, but meant different tools were used and processes followed).
This microservice, which I believe was initially generated by some IBM tool (Appsody?), has stuff in its pom.xml and elsewhere that refers to Cloud Foundry, Bluemix, and some IBM-proprietary monitoring. I don't have time at the moment to go find and remove all o this and test it all, but opening this as a reminder. The intention is that, like all of the other Stock Trader microservices, this one should be focused on Kubernetes, Jakarta, and MicroProfile and do things in industry-standard ways that would work on any cloud, rather than bundling in stuff like for agents for some IBM proprietary monitoring products. Need to do a review and cleanup of this microservice to bring it in line with the ones written by the Cloud Journey Optimization Team (this one was contributed by people on the Liberty team, which was appreciated, but meant different tools were used and processes followed).