anchor.diff:  An application with the name, `myApp`, would have any properties written to `secret/myApp` and `secret/application` available to it.
   When `myApp` has the `dev` profile enabled, properties written to all of the above paths would be available to it, with properties in the first path in the list taking priority over the others.
   
  +==== Accessing Backends Through a Proxy
  +
  +The configuration server can access a Git or Vault backend through an HTTP or HTTPS proxy. This behavior is controlled for either Git or Vault by settings under `proxy.http` and `proxy.https`. These settings are per repository, so if you are using a <<composite-environment-repositories,composite environment repository>> you must configure proxy settings for each backend in the composite individually. If using a network which requires separate proxy servers for HTTP and HTTPS URLs, you can configure both the HTTP and the HTTPS proxy settings for a single backend.
  +
  +The following table describes the proxy configuration properties for both HTTP and HTTPS proxies. All of these properties must be prefixed by `proxy.http` or `proxy.https`.
  +
  +.Proxy Configuration Properties
  +|===
  +|Property Name |Remarks
  +
  +|*host*
  +|The host of the proxy.
  +
  +|*port*
  +|The port with which to access the proxy.
  +
  +|*nonProxyHosts*
  +|Any hosts which the configuration server should access outside the proxy. If values are provided for both `proxy.http.nonProxyHosts` and `proxy.https.nonProxyHosts`, the `proxy.http` value will be used.
  +
  +|*username*
  +|The username with which to authenticate to the proxy. If values are provided for both `proxy.http.username` and `proxy.https.username`, the `proxy.http` value will be used.
  +
  +|*password*
  +|The password with which to authenticate to the proxy. If values are provided for both `proxy.http.password` and `proxy.https.password`, the `proxy.http` value will be used.
  +|===
  +
  +The following configuration uses an HTTPS proxy to access a Git repository.
  +
  +[source,yaml]
  +----
  +spring:
  +  profiles:
  +    active: git
  +  cloud:
  +    config:
  +      server:
  +        git:
  +          uri: https://github.com/spring-cloud-samples/config-repo
  +          proxy:
  +            https:
  +              host: my-proxy.host.io
  +              password: myproxypassword
  +              port: '3128'
  +              username: myproxyusername
  +              nonProxyHosts: example.com
  +----
  +
   ==== Sharing Configuration With All Applications
   
   Sharing configuration between all applications varies according to which approach you take, as described in the following topics:
  
positive.code: A value found in the `rex` Git repository will be used before a value found for the same property in the `walter` Git repository.
  
  If you want to pull configuration data only from repositories that are each of distinct types, you can enable the corresponding profiles, rather than the `composite` profile, in your configuration server's application properties or YAML file.
  If, for example, you want to pull configuration data from a single Git repository and a single Subversion repository, you can set the following properties for your configuration server:
  
  [source,yaml]
  ----
  spring:
    profiles:
      active: git, subversion
    cloud:
      config:
        server:
          git:
            uri: file:///path/to/git/repo
            order: 2
          svn:
            uri: file:///path/to/svn/repo
            order: 1
  ----
  
  
negative.code: All fields are of type String in Java, so you can make them `VARCHAR` of whatever length you need.
  Property values behave in the same way as they would if they came from Spring Boot properties files named `{application}-{profile}.properties`, including all the encryption and decryption, which will be applied as post-processing steps (that is, not in the repository implementation directly).
  
  [[composite-environment-repositories]]
  ==== Composite Environment Repositories
  
  In some scenarios, you may wish to pull configuration data from multiple environment repositories.
  