Add SlaveID field in Task struct

[ohmystack]

Marathon has a "slaveId" field in "task" since v0.11.0-RC1

[ohmystack]

Sorry. I'll pull the latest master and fix the conflict.

[ohmystack]

Fixed.

@gambol99 @timoreimann @bobrik, would you mind reviewing?

[timoreimann]

We don't seem to use the majority of the message fields defined in the YML spec. In fact, I can remove the slaveId properties (and many others) without any tests turning red.

IMHO, we need tests that make sure our deserialization is working correctly. Along the way, we can probably clean up a lot of YML code.

Thus, my suggestion would be to not include the slaveId properties in the YML file, merge the PR, and create an issue to improve deserialization testing separately. @gambol99, WDYT?

Apart from this open question, the PR LGTM. 👍

[ohmystack]

@timoreimann That makes sense. In the new change, I've removed the slaveId in YML file.

[timoreimann]

Thanks, appreciate the contribution!

[ohmystack]

@timoreimann 😀 Thanks to you