From bda67f235c764f53ce2596607dad35e1a5f9c01f Mon Sep 17 00:00:00 2001 From: Ryan Baxter Date: Tue, 5 Jun 2018 10:57:33 -0400 Subject: [PATCH] Clarify property overrides. --- docs/src/main/asciidoc/spring-cloud-commons.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/main/asciidoc/spring-cloud-commons.adoc b/docs/src/main/asciidoc/spring-cloud-commons.adoc index 9672eaec..d366dc69 100644 --- a/docs/src/main/asciidoc/spring-cloud-commons.adoc +++ b/docs/src/main/asciidoc/spring-cloud-commons.adoc @@ -87,12 +87,12 @@ context you are building), properties in that profile get loaded as well, the sa === Overriding the Values of Remote Properties The property sources that are added to your application by the bootstrap context are often "`remote`" (from example, from Spring Cloud Config Server). -By default, they cannot be overridden locally, except on the command line. +By default, they cannot be overridden locally. If you want to let your applications override the remote properties with their own System properties or config files, the remote property source has to grant it permission by setting `spring.cloud.config.allowOverride=true` (it does not work to set this locally). Once that flag is set, two finer-grained settings control the location of the remote properties in relation to system properties and the application's local configuration: * `spring.cloud.config.overrideNone=true`: Override from any local property source. -* `spring.cloud.config.overrideSystemProperties=false`: Only system properties and environment variables (but not the local config files) should override the remote settings. +* `spring.cloud.config.overrideSystemProperties=false`: Only system properties, command line arguments, and environment variables (but not the local config files) should override the remote settings. === Customizing the Bootstrap Configuration