5 Commits

Author	SHA1	Message	Date
Vincent Bernat	c44ed88659	GANDI_V5 & DESEC: correctly handle multiple RR in a RRset (#1296) ... When having multiple RR in a RRset, only a few of them may be applied. In my case, when I have two A records, only one of them makes its way to Gandi. In `convert.go`, we had: ```go var zrs []livedns.DomainRecord // [...] zrs = append(zrs, zr) keys[key] = &zrs[len(zrs)-1] ``` If the slice needs to be extended when appending, the reference we got in `keys[key]` may be outdated because the new slice contains a copy of the old one. We either need to store references to domain records in the slice or we need to stop keeping reference of items in the slice. I have fixed this with the second solution as I think the order of the RRsets is not important.	2021-11-01 15:41:37 -04:00
Tom Limoncelli	d5bfee9f1e	Maint: DS record tests should use more realistic data (#1127) ... * DS tests should use real hashes * Increase integration test timeout to 20m	2021-04-17 10:49:06 -04:00
nemunaire	ce6006cce7	GANDI_V5 & OVH: Implement ZoneLister (#1117) ... * GANDI_V5: implement ZoneLister * OVH: implement ZoneLister	2021-04-03 10:31:25 -04:00
Phil Pennock	059b58ed9e	GANDI_V5: supports DS records already (#1112) ... * Simply mark DS as supported, let existing tests handle it. * Fix trivial typo in diagnostic feedback from model SetTargetDSString() * The support matrix includes more changes because it was stale.	2021-03-29 10:04:36 -04:00
Tom Limoncelli	e69e6f27e4	Linting (#1087) ... * fix linting * rename AuditRecordsor to RecordAuditor * gandi_v5 to gandiv5	2021-03-08 20:14:30 -05:00