Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.
Sometimes you want the clients to decrypt the configuration locally,
+instead of doing it in the server. In that case you can still have
+/encrypt and /decrypt endpoints (if you provide the encrypt.*
+configuration to locate a key), but you need to explicitly switch off
+the decryption of outgoing properties using
+spring.cloud.config.server.encrypt.enabled=false. If you don’t care
+about the endpoints, then it should work if you configure neither the
+key nor the enabled flag.
The Config Server runs best as a standalone application, but if you need to you can embed it in another application. Just use the @@ -1235,7 +1249,6 @@ initialize the same way as any other application.