* Switch to aws-sdk-go-v2
AWS has released v2 of their SDK for Go.
See: https://aws.github.io/aws-sdk-go-v2/
One big advantage of this is no longer needing to export the
`AWS_SDK_LOAD_CONFIG=1` env var when using named profiles.
* Update integration test README
* Reenable pager601 and pager1201 integration tests for AWS Route53
* Implement intelligent batching for Route53 record changes
The AWS Route53 API for batch record changes limits the request size to
the smaller of:
- 1000 records.
- 32000 characters total for record values.
Also UPSERTs count as double (a DELETE and then a CREATE).
This commit changes how the record ChangeBatches are created to
respect these limits.
* Remove old comments
Co-authored-by: Tom Limoncelli <tlimoncelli@stackoverflow.com>
* Remove length checking from TxtNoMultipleStrings
All functions in should test for only one condition. There already is a
function that tests for long TXT records: TxtNoLongStrings.
Add calls to TxtNoLongStrings in all providers that use
TxtNoMultipleStrings, to keep functionality, except for NS1 and ClouDNS,
which allow for any TXT record length, but not for multiple strings per
TXT.
* Release v3.13.0
* Release v3.13.0
Co-authored-by: Norman Stetter <norman.stetter@zeit.de>
* First pass at moving to cloudflare-go vs hand made implementation of cloudflare's API
* Final changes to use cloudflare-go
* Fix for proxy configuration failing
Forgot to set the ID when we created a new records. This didn't fail in the integrations tests so I missed it.
* Add integration test
To prevent something like what I did from happening in the future.
* Fix bad messaging
REGRESSION and BUILD fix. dnscontrol compiles with this but I can't test the
EXOSCALE behavior to be sure it's logically sound.
The dependency was v1.19.0 but this git tag has been withdrawn and the go.mod
for that git repository contains:
retract v1.19.0 // Published accidentally.
Per <https://proxy.golang.org/github.com/exoscale/egoscale/@v/v1.19.0.info> the
timestamp for the bogus v1.19.0 dependency is 2019-10-29, which corresponds to
v0.19.0.
On 2020-02-27, the dnscontrol repo updated this dependency to v0.23.0, so it
now being v1.19.0 (== v0.19.0) is a REGRESSION.
I suggest that the maintainers purge this bogus v1.19.0 from their systems to
try to prevent it leaking in again in future.
TXT records are now handled different.
1. The raw input from dnsconfig.js is passed all the way to the provider. The provider can determine if it can or can't handle such records (auditrecords.go) and processes them internally as such.
2. The CanUseTXTMulti capability is no longer needed.
* DSPs now register a table of functions
* Use audits for txt record variations
* unit tests pass. integration fails.
* fix deepcopy problem
* rename to AuditRecordSupport
* Reduce use of TXTMulti
* Remove CanUseTXTMulti
* fix Test Skip
* fix DO
* fix vultr
* fix NDC
* msdns fixes
* Fix powerdns and cloudflare
* HEDNS: Fix usage of target field to resolve TXT handling (#1067)
* Fix HEXONET
Co-authored-by: Robert Blenkinsopp <robert@blenkinsopp.net>
Co-authored-by: Jakob Ackermann <das7pad@outlook.com>
FYI: This is an experimental feature. It depends on an external module that may not be supported in the long term.
* PoC: JS formatter
* No default value for output file
