anchor.diff:  
   |===
   
  -
  -===== Official Consul Metadata
  -
  -Consul added official support for a `meta` field that is a `Map<String, String>`. Spring Cloud Consul has added `spring.cloud.consul.discovery.metadata` and `spring.cloud.consul.discovery.management-metadata` properties to support it.
  -
  -NOTE: By default, the `ServiceInstance.getMetadata()` method from Spring Cloud Commons will continue to populated by parsing the `spring.cloud.consul.discovery.tags` property for backwards compatibility. To change this behaviour set `spring.cloud.consul.discovery.tags-as-metadata=false` and the metadata will be populated from `spring.cloud.consul.discovery.metadata`. In a future version, parsing the `tags` property will be removed.
  +WARNING: Older versions of Spring Cloud Consul populated the `ServiceInstance.getMetadata()` method from Spring Cloud Commons by parsing the `spring.cloud.consul.discovery.tags` property. This is no longer supported, please migrate to using  the `spring.cloud.consul.discovery.metadata` map.
   
   ==== Making the Consul Instance ID Unique
   
  
positive.code: 
  You can disable the health check by setting `management.health.consul.enabled=false`.
  
  ==== Metadata and Consul tags
  
  Consul does not yet support metadata on services. Spring Cloud's `ServiceInstance` has a `Map<String, String> metadata` field. Spring Cloud Consul uses Consul tags to approximate metadata until Consul officially supports metadata. Tags with the form `key=value` will be split and used as a `Map` key and value respectively. Tags without the equal `=` sign, will be used as both the key and value.
  
  .application.yml
  ----
  
negative.code:   cloud:
      consul:
        discovery:
          metadata:
            myfield: myvalue
            anotherfield: anothervalue
  ----
  
  The above configuration will result in a service who's meta field contains `myfield->myvalue` and `anotherfield->anothervalue`.
  
  ===== Generated Metadata
  
  