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
* govendor gopkg.in/yaml.v2
* Ignore YAML and BIND test data litter. Create README.txt files to force git to create subdirectories.
* Update convertzone to also read OctoDNS files
This appears to be the only one. Manual audit with (zsh):
pcregrep -o1 '}}/([^\)]+)\)' **/*(.)
yielded all the site-based URLs and I eye-compared them to the names of
existing docs.
* intitial work for bind refactor
* relax requirement that creds.json exists.
* Updating bind docs.
Fixes#48
* typo
* can exclude provider from default set in creds.json
* Add bind to integration tests. Fix for IDNs.
