You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resolving configuration from the Spring Cloud Config server at runtime is not that easy anymore since it requires the use of legacy support org.springframework.cloud:spring-cloud-starter-bootstrap in latest releases. The thing is that OpenWMS.org uses the Service Registry First approach https://github.com/openwms/org.openwms/wiki/Secured-Eureka-First-services-on-Heroku#eureka-first-bootstrap. Only basic configuration is obtained at compile-time and all other required configuration is fetched at runtime. This is an issue for pre-compiled and pre-linked executables, because all runtime config must exist at build-time.
The text was updated successfully, but these errors were encountered:
Hi @cloorc . Thank you for your interest. Have a look at Spring profiles. Some services use Spring profiles for kinda "feature toggling". Running them with profile DISTRIBUTED means in a microservice architecture. Bundling them into a WAR and running the whole application not DISTRIBUTED and STANDALONE means monolithic and all-in-one. Regarding the wiki link, thanks for the reminder, I've to rebuild all pages in wiki
Currently all the services use a version 2.7.x
Resolving configuration from the Spring Cloud Config server at runtime is not that easy anymore since it requires the use of legacy support
org.springframework.cloud:spring-cloud-starter-bootstrap
in latest releases. The thing is that OpenWMS.org uses the Service Registry First approachhttps://github.com/openwms/org.openwms/wiki/Secured-Eureka-First-services-on-Heroku#eureka-first-bootstrap
. Only basic configuration is obtained at compile-time and all other required configuration is fetched at runtime. This is an issue for pre-compiled and pre-linked executables, because all runtime config must exist at build-time.The text was updated successfully, but these errors were encountered: