v0.2.0

Full Changelog: v0.1.1...v0.2.0

• New client
• New Storage interface

v0.1.1

goacmedns v0.1.1

storage: persist API server URL alongside Account details

In this patch release the Account struct was updated to also track the acme-dns server URL the account was registered with.

The new functionality allows account storage to be self sufficient for all the required data points. While the API server URL can often be deducted from the account URL, it's not guaranteed.

Thanks to @joohoi for this new feature.

v0.1.0

goacmedns v0.1.0

storage: add FetchAll to Storage interface

In this minor release a new FetchAll function was added to the Storage interface and fileStorage implementation. This function supports returning all managed Account instances from the storage.

Thanks to @joohoi for this new feature.

v0.0.3

fix: respect system http proxy settings.

Adds Proxy: http.ProxyFromEnvironment to the http.Client.Transport instance used by goacmedns when connecting to the ACME-DNS server. This allows using goacmedns in an environment that restricts egress traffic to a proxy server.

Thanks to @christiancorbin for the fix.

v0.0.2

fix: match JSON Account serialization to pyacmedns/acmedns.

Prior to this v0.0.2 release the Account objects marshalled to/from JSON by the goacmedns file storage used JSON keys with capitalization that differs from the pyacmedns JSON storage, and the register response from acme-dns (e.g. Domain vs domain).

This release fixes that by updating the Account type to add explicit json tags that ensure the capitalization of the fields matches that of pyacmedns and acme-dns. Go's JSON parsing semantics ensures legacy accounts with capitalized fields will still load without error.

Thanks to @emilazy for filing an issue about the divergence.

v0.0.1

util: support -allowFrom in goacmedns-register