Deprecate running container with command

Before, we were instructing people to run the container using the actual command and arguments. That's now deprecated, and instead you only need to specify the right environment variables.

The old method still works, so won't break any deployments as long as we're on the 3.x series.

Cron removal

When I wrote kong-certbot-agent originally, it was to plug a very specific need: I needed to provision LE certs into Kong in a Kubernetes 1.3 project I was working on at the time, which didn't have any sort of job scheduling capabilities. Hence, the image contained cron so that a regular, always-on kubernetes deployment could be used to achieve the same effect.

It's now been a long time since Kubernetes has job scheduling capabilities, even if they're still in the beta api stage. And any other system you might be deploying the agent on will likely have similar capabilities.

Thus, I've now removed cron, its crontab and the kubernetes cron'd deployment from kong-certbot-agent. Any scheduling of the agent must now be external to kong-certbot agent.

If you still need the containers that have cron, please use the 2.x series. The last version of that series is 2.3.6 - 3.0.0 is the exact same code, minus all the cron stuff.

2.2.0 - Major internal refactor

Kong certbot agent has proved way more popular than I thought it would be, and a number of small but breaking problems have been creeping up as Kong approaches its v1.0 release. There was a need for more quality control, or rather, for quality control (period).

This version brings a major internal refactor to allow for a good battery of tests to be run against any code changes. I've found a myriad of small issues while doing this and hopefully fixed others. The new tests will make it way easier to fix and change stuff in the future.

This is just a minor version bump (from 2.1.x to 2.2.0) though as it's 100% backwards compatible with both command line and Kong 0.14.

Changes:

• Split code into different concerns
• Test each concern separately
• Test the whole app as a function
• Add to CI
• Add coverage metrics
• Ensure contributor's fixes are all in
• Fix:
  • Certificate collisions
  • Error resiliance during collisions - now certs can be saved per domain when this happens
  • Error reporting

SNI Updates: compatible with Kong 0.14

Kong recently updated their certificate admin API around the shape of the snis property. This release makes us compatible with it.

Requires Kong Community Edition 0.14+.

Actually merge the code in question

Note to self: double check stuff when cutting releases at the end of a working day.

Use newer snis format

This unfortunately is a breaking change.