anchor.diff:  Several locations can be specified under a single `spring.config.import` key.
   Locations will be processed in the order that they are defined, with later imports taking precedence.
   
  -NOTE: When appropriate, <<boot-features-external-config-files-profile-specific, Profile-specific variants>> are also considered for import.
  +NOTE: When appropriate, <<features#features.external-config.files.profile-specific, Profile-specific variants>> are also considered for import.
   The example above would import both `my.properties` as well as any `my-<profile>.properties` variants.
   
   [TIP]
  
positive.code: 
  [NOTE]
  ====
  The last-wins strategy applies at the <<features.external-config.files.location-groups,location group>> level.
  A configprop:spring.config.location[] of `classpath:/cfg/,classpath:/ext/` will not have the same override rules as `classpath:/cfg/;classpath:/ext/`.
  
  For example, continuing our `prod,live` example above, we might have the following files:
  
negative.code: At runtime they will be appended with the names generated from `spring.config.name` before being loaded.
  Files specified in `spring.config.location` are imported directly.
  
  NOTE: Both directory and file location values are also expanded to check for <<features#features.external-config.files.profile-specific,profile-specific files>>.
  For example, if you have a `spring.config.location` of `classpath:myconfig.properties`, you will also find appropriate `classpath:myconfig-<profile>.properties` files are loaded.
  
  In most situations, each configprop:spring.config.location[] item you add will reference a single file or directory.
  