v1.0.0

With the full 1.0.0 release of the provider, we have shifted support over to ACME v2. Amongst other things, this also means that the provider now supports wildcard certificates!

There were a number of other changes, so make sure to check the CHANGELOG, and the documentation.

NOTE: This version of the provider does not support ACME v1. If you still need ACME v1, use version 0.6.0.

v0.6.0

This is the final release until 1.0.0, which will remove support for ACME v1 and replace it with ACME v2. Hence, this is the final release of the provider if you wish to use ACME v1.

There have been a number of fixes, and we have refreshed lego against version v0.5.0, which is the last release before ACME v2 was merged.

For all the details, see the CHANGELOG.

v0.5.0

This is mainly a refresh of the lego package that we use in the provider, along with the items it provides. See CHANGELOG.md for more details.

Also, releases are being signed again, this time with @vancluever's own personal signing key, which you can get from here. The specific fingerprint is CFED9BDD618AFC92C28A3CDA335B84AFEC615CE4.

v0.4.0 - Improved Certificate Diff Behaviour

This release ships with the custom diff support Terraform patch to help facilitate the correct behaviour for when a certificate expires. See the CHANGELOG for more details.

Note a couple of other things:

• Releases are no longer being signed, so if you see a missing signature that's why. Signing may come back under a dedicated signing key at a later date.
• The plugin has been built against Terraform v0.10.0-beta2 and while not much has changed under the hood, YMMV with using versions below this. Note in particular the plugin version has not changed and nothing is being sent over the plugin RPC connection that should be unaccounted for, but please report any issues you find!

v0.3.0 - Supporting TF v0.9.0

Fully updated version, supporting v0.9.0. Make sure you use this version for the full v0.9.0 release, as v0.3.0-beta2 will not work (the plugin API version has been incremented again). People still on versions of TF before v0.9.0 should use a v0.2.x version.

0.3.0-beta2

This beta version tracks Terraform v0.9.0, which as of this writing (Feb 28th, 2017) is currently in beta. All that has changed so far on this side is that we need to rebuild as the plugin API has again changed.

v0.2.1

This is a bugfix to correct #6 and ensure that TF will abort if a DNS challenge is improperly configured (example: missing credentials). Previous to this release if the DNS challenge could not be properly set up, the plugin would have proceeded with an HTTP or TLS challenge.

v0.2.0

Note that this release is built for Terraform v0.8.0 and higher - using with v0.7.x and lower may not work. Use the v0.1.0 release instead.

• Added the must_staple option - this option adds the OCSP Stapling Required extension to created certificates, ensuring that a valid OCSP Staple must be included in the TLS handshake for the connection to proceed. This is disabled by default. This option has no effect when being used with external CSRs.

v0.1.0

Add CHANGELOG.md