Conversation
…where new records could not be created
There was a problem hiding this comment.
Looks like there are some incompatible changes in latest commits - libdns/gandi@5a26022
I guess it is a mess we will have to bring downstream by breaking config compatibility as it is no longer possible to specify an API key in libdns/gandi despite them being still supported.
Also, libdns/gandi maintainer overwrites existing releases, leading to issues with Go tooling (#555, libdns/gandi#9), therefore it is important to specify a particular commit in go.mod using pseudoversions.
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #673 +/- ##
==========================================
- Coverage 52.49% 52.43% -0.06%
==========================================
Files 128 128
Lines 13311 13324 +13
==========================================
Hits 6987 6987
- Misses 5667 5680 +13
Partials 657 657
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
Thanks for your work! |
upgraded to the latest version of gandi libdns, which fixes an issue where new records could not be created
See #619