anchor.diff:  ----
   greeting.message = hello
   greeting.name = quarkus
  -greeting.hidden.prize-amount=10
  -greeting.hidden.recipients=Jane,John
  +greeting.content.prize-amount=10
  +greeting.content.recipients=Jane,John
   ----
   
   Furthermore, classes annotated with `@ConfigProperties` can be annotated with Bean Validation annotations similar to the following example:
  
positive.code: For example, consider the two configuration properties `quarkus.http.cors` and `quarkus.http.cors.methods`.
  One property is the prefix of another, so it may not be immediately evident how to specify both keys in your YAML configuration.
  
  This is solved by using a null key (normally represented by `~`) for any YAML property which is a prefix of another one.  Here's an example:
  
  .An example YAML configuration resolving prefix-related key name conflicts
  [source,yaml]
  
negative.code:       methods: GET,PUT,POST
  ----
  
  In general, `null` YAML keys are not included in assembly of the configuration property name, allowing them to be used to
  any level for disambiguating configuration keys.
  
  == More info on how to configure
  