Releases: remilapeyre/vault-acme
Releases · remilapeyre/vault-acme
Release v0.0.9
Update changelog for the 0.0.9 release
Release v0.0.8
Return more informative error message on failure
Release v0.0.7
Make it possible to update an ACME account Closes https://github.com/remilapeyre/vault-acme/issues/22
Release v0.0.6
Add provider_configuration parameter to override environment variables Closes https://github.com/remilapeyre/vault-acme/issues/19
Release v0.0.5
Add a SHA256SUMS file in the releases Closes https://github.com/remilapeyre/vault-acme/issues/17
Release v0.0.4
Add account flag to ignore waiting for DNS propagation Provide a way to let lego ignore the check for DNS propagation. The default remains `false` (default value of library): wait until the DNS changes have been propagated to all authoritative DNS servers. Existing vault accounts should continue to work (new flag will be set to `false` if it does not exists). This option might be helpful/required for specific setups/situation where this does not work correctly (like specific split-horizon setups etc). The `ignore_dns_propagation` option behaves as the underlaying `--dns.cp-disable` command line LEGO flag.
Release v0.0.3
Add support for different types of private keys for the account This change the data associated with the account so all accounts will need to be destroyed and recreated before requesting a new certificate: $ vault delete acme/accounts/lenstra $ vault write acme/accounts/lenstra contact=remi@lenstra.fr ... Closes https://github.com/remilapeyre/vault-acme/issues/12
Release v0.0.2
Disable CGO support Closes https://github.com/remilapeyre/vault-acme/issues/11
Release v0.0.1
Publish release on tags