4.1.1

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

Update default health check protocol

"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.html#marathon-level-health-checks

Require full vault paths when resolving secrets

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.

3.2.0 - Labels, labels, labels

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.

3.1.3

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.

3.1.1 - Bridge over troubled water

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.

3.1.0 - Run, shpkpr, run!

This release includes a number of small improvements and one new command.

Changes:

• Improve deployment logging.
• Add secrets block to default Chronos job template.
• Auto-publish to PyPI using Travis CI.

New features:

• New apps run command to allow running one-off commands with deployment configuration.

3.0.0 - Ports? What ports?

This release contains a single large changeset. It is no longer necessary to specify a pair of "service ports" when performing a blue/green deployment.

If not specified, shpkpr will automatically choose two free ports at random. If updating an existing deployed application, shpkpr will reuse the ports that have already been assigned.

Whilst we've tested this feature thoroughly it's quite a large change, please test yourself before upgrading.

2.0.0 - The saga continues

This release contains a number of important features for users. The CLI API has changed slightly and so this is considered a breaking change (hence the 2.0).

Changes:

• Major refactor of deployment code
• Logging refactor

Features:

• HTTP Basic Auth for both Chronos and Marathon
• Built-in default templates for standard and bluegreen deploys as well as Chronos tasks
• Much better/more complete documentation for the CLI
• New slugify template filter

And much more! Check it out at all the usual places!

1.0.0 - Yay!

Finally, a 1.0 release.

Hot off the presses: https://pypi.python.org/pypi/shpkpr

This release includes:

• Marathon:
  • List apps
  • Show app details
  • Deploy applications using templates
  • Zero-downtime deployments with Marathon LB
• Chronos
  • List tasks
  • Show task details
  • Deploy tasks with templates

This release is a stepping-stone to a number of future improvements and you shouldn't really give any significance to the version number. From here on out we'll be using semantic versioning where possible.