This makes it clear that the dockerswarm package does more than docker swarm, but does also docker. I have picked moby as it is the upstream name: https://mobyproject.org/ There is no user-facing change, except in the case of a bad configuration. Previously, a user who would have a bad docker sd config would see an error like: > field xx not found in type dockerswarm.plain Now that error would be turned into: > field xx not found in type moby.plain While not perfect, it should at not be confusing between docker and dockerswarm. Signed-off-by: Julien Pivotto <roidelapluie@inuits.eu> |
||
---|---|---|
.. | ||
_ping.json | ||
headers.yml | ||
networks.json | ||
nodes.json | ||
services.json | ||
services.json__wvKVCQ4HhD | ||
tasks.json |