anchor.diff:    cloud:
       consul:
         discovery:
  -        tags: foo=bar, baz
  -----
  -
  -The above configuration will result in a map with `foo->bar` and `baz->baz`.
  +        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
   
  
positive.code: 
  |===
  
  
  ===== 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.
  
  ==== Making the Consul Instance ID Unique
  
  
negative.code: 
  You can disable the health check by setting `management.health.consul.enabled=false`.
  
  ==== Metadata
  
  Consul supports metadata on services. Spring Cloud's `ServiceInstance` has a `Map<String, String> metadata` field which is populated from a services `meta` field. To populate the `meta` field set values on `spring.cloud.consul.discovery.metadata` or `spring.cloud.consul.discovery.management-metadata` properties.
  
  .application.yml
  ----
  