It looks like marathon 0.11 uses Id instead of taskId. This causes `<no value>` to be set in the haproxy.cfg file when marathon mode is enabled.
It looks like marathon 0.11 uses Id instead of taskId. This causes
<no value>to be set in the haproxy.cfg file when marathon mode is enabled.