SpringCloud/spring-cloud-config
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix formatting errors

Browse Source
This commit is contained in:
Dave Syer
2014-10-02 11:39:10 +01:00
parent 9730c84b6d
commit 1dc89582a8
2 changed files with 9 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.adoc
View File

@@ -1,4 +1,4 @@
// Do not edit this file (go instead to src/main/asciidoc)
// Do not edit this file (e.g. go instead to src/main/asciidoc)
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.

13
src/main/asciidoc/spring-cloud-config.adoc
View File

@@ -94,9 +94,11 @@ values in remote repositories).
To configure an asymmetric key you can either set the key as a
PEM-encoded text value (in `encrypt.key`), or via a keystore (e.g. as
created by the `keytool` utility that comes with the JDK). The
keystore properties are `encrypt.keyStore.*` with `*` equals to
`location` (a `Resource` location), `password` (to unlock the
keystore) and `alias` (to identify which key in the store is to be
keystore properties are `encrypt.keyStore.\*` with `*` equal to
* `location` (a `Resource` location),
* `password` (to unlock the keystore) and
* `alias` (to identify which key in the store is to be
used).
The encryption is done with the public key, and a private key is
@@ -189,7 +191,7 @@ individual bean by name. This functionality is exposed in the
The Config Client has an `Environment` pre-processor for decrypting
property values locally. It follows the same rules as the Config
Server, and has the same external configuration via `encrypt.*`. Thus
Server, and has the same external configuration via `encrypt.\*`. Thus
you can use encrypted values in the form `{cipher}*` and as long as
there is a valid key then they will be decrypted before the main
application context gets the `Environment`.
@@ -197,6 +199,7 @@ application context gets the `Environment`.
=== Endpoints
For a Spring Boot Actuator application there are some additional management endpoints:
* POST to `/env` to update the `Environment` and rebind `@ConfigurationProperties` and log levels
* `/refresh` for re-loading the boot strap context and refreshing the `@RefreshScope` beans
* `/restart` for closing the `ApplicationContext` and restarting it (disabled by default)
@@ -210,7 +213,7 @@ the box it is responsible for loading configuration properties from
the Config Server, and also decrypting properties in the local
external configuration files. The two contexts share an `Environment`
which is the source of external properties for any Spring
application. Bootstrap properties are added with hight precedence, so
application. Bootstrap properties are added with high precedence, so
they cannot be overridden by local configuration.
The bootstrap context uses a different convention for locating