Optima Config Server¶
Spring Cloud Config provides server-side and client-side support for externalized configuration in a distributed system.
Integration with existing modules - Optima Gateway and Admin Console¶
We've successfully integrated config server with existing modules and we can try to look at
the configurations - based upon the application, profile and label:
curl <config-server-uri>/<application-name>/<profile>/<label>
Validating externalized configurations - config server instance available on DEV¶
curl https://optima-dev-tenants.optumrx.com/config/admin-console/local/master
OR
curl https://optima-dev-tenants.optumrx.com/config/admin-console/local
Validating externalized configurations - config server running on localhost¶
Environment variables : running a local instance for config server¶
GIT_USERNAME: <Github user with access to Optima Configurations>
GIT_PASSWORD: <Github personalized access token for a user with access to Optima Configurations>
OPTIMA_CONFIG_SERVER_USERNAME: <Username for a client to access the config server>
OPTIMA_CONFIG_SERVER_PASSWORD: <Password for a client to access the config server>
Search Paths: implementation for various modules within config server¶
search-paths: '{application}'
where:
application = application-name specified for any specific application module
e.g. gateway-v2, gateway-v3 or admin-console
Base directory: used by the spring cloud config to clone the configurations¶
/tmp/config - is the directory available at root location used by the config server
to perform a clone for the externalized configurations before injecting them
to client applications
Additional References¶
In order to learn and have an in-depth understanding about the details related to Spring Cloud Config Server, please consider the following sections:
- Official Apache Maven documentation
- Spring Boot Maven Plugin Reference Guide
- Create an OCI image
- Config Server
Guides¶
The following guides illustrate how to use some features concretely: