Cloudflare API tokens are a new way to authenticate to Cloudflare API.
Unlike the Global API key, tokens can be given specific permissions to
only access parts of the API. See [1] for details.
[1] https://blog.cloudflare.com/api-tokens-general-availability/
This commit introduces a new credential for cloudflare called
`apitoken`, which is mutually exclusive with `apiuser` and `apikey`.
In order for DNSControl to work with this token, it should have the
right to read DNS zones and edit DNS records.
Closes#534
* docs improvements
* Updated matrix as part of "go generate" (e.g. adds SSHFP row)
* Commiting full matrix file
* Added docs for SSHFP record
* Matrix: Mark OVH as SSHFP-capable in docs (see PR #482)
- Fixed indentation
- Use same naming scheme for all examples
(i.e. all caps for provider, REG prefix for registrar)
- Use REG_NONE as registrar when provider does not provide it
- Use example.tld for example domain
- Use 1.2.3.1/24 IP range for examples
- A few spelling fixes
* function sig
* sig
* some custom record infrastructure
* CLOUDFLARE REDIRECTS!
* comments out
* guarding redirects behind provider metadata to manage
* catch commas in js to ensure proper encoding.
* gen
* small fix
* revendor otto
* docs
* Clarify what "apiuser" is in Cloudflare docs
Confusingly it is the email address associated with the account, not the username.
* Remove Gandi registrar from docs
Because it doesn't actually exist.
