Shpkpr

This release changes the default deploy template to use MAX_PER instead of GROUP_BY when defining constraints.

"MESOS_HTTP", "MESOS_HTTPS" and "MESOS_TCP" are now the recommended health check protocols. This allows health checks to be run by the agent instead of the Marathon master. This can help to reduce load on it.

https://mesosphere.github.io/marathon/docs/health-checks.htmlmarathon-level-health-checks

Prior to v4.0.0, `secret/` was prepended to all vault paths. Starting in v4.0.0, `secret/` is no longer prepended to the vault path.

If you are using v3.2.0 (or below) of shpkpr, your application may break in v4.0.0 if you use any vault/secrets functionality.

This release fixes an issue with an incompatible docker-py dependency and ensures Marathon labels are also added as Docker labels when using the default template.

This release includes a small change to behavior when retrieving secrets from Vault - when a secret is missing, shpkpr will now log a missed entry in Vault, rather than failing. This ensures that the `shpkpr apps run` will continue in the presence of a missing, non-essential secret, such as an additional private key used for rotation.

This bugfix release modifies the `shpkpr apps run` command to always use `bridge` networking for the containers it starts up.

This prevents the port collisions we currently see when using `host` networking mode.