Services built on Light Frameworks are composed of many plugins as part of the embedded gateway. Each plugin (or middleware handler) has its configuration file and runtime behaviour to control if they are enabled. Developers usually don’t need to worry about these config files as these can be added later on by the operation team in the DevOps pipeline.
Unlike other application frameworks, we are not using a single config file but multiple config files because each service decides which plugins should be utilized and how they are utilized.
When managing the configurations, the following things need to be considered:
- Multiple config template files per service.
- Every environment has some different values.
- Different release tags of the service will have different configurations.
- Some sensitive values need to be encrypted.
- Some of the config files need to be merged from several organizations.
- Some of the config files need to be overwritten from several organizations.
- When the config server is used, there should be minimum internal config files to ensure the connectivity to the config server
For more information on how to use the Config Server, please visit the tutorial section.