anchor.diff:  ./mvnw quarkus:generate-config -Dfile=application.properties
   --
   
  -If a config option is already present (commented or uncommented) it will not be added, so it is safe to run this after
  +If a config option is already present (commented or not) it will not be added, so it is safe to run this after
   adding an additional extension to see what additional options have been added.
   
   == Overriding properties at runtime
  
positive.code: === Configuration Profiles
  
  Quarkus supports the notion of configuration profiles. These allow you to have multiple configuration in the same file and
  select between then via a profile name.
  
  The syntax for this is `%{profile}.config.key=value`. For example if I have the following:
  
  
negative.code: There are two ways to set a custom profile, either via the `quarkus.profile` system property or the `QUARKUS_PROFILE`
  environment variable. If both are set the system property takes precedence. Note that it is not necessary to
  define the names of these profiles anywhere, all that is necessary is to create a config property with the profile
  name, and then set the current profile to that name. For example if I want a `staging` profile with a different HTTP port
  I can add the following to `application.properties`:
  
  [source,properties]
  