Add new dnsapi support for OpenProvider.eu using new REST API
This add support for OpenProvider.eu / .com using their newer REST API.
With this newer version there is no full DNS zone update needed anymore (including existing A, AAAA, CAA, CNAME, MX, NS, PTR, SOA, SRV, and TXT) for a single validation request.
Only the single TXT record is added and removed for the validation request.
_Note: added as new dnsapi option as the original SOAP/XML API is still online and working with dns_openprovider.sh
Welcome First thing: don't send PR to the master branch, please send to the dev branch instead. Please make sure you've read our DNS API Dev Guide and DNS-API-Test. Then reply on this message, otherwise, your code will not be reviewed or merged. We look forward to reviewing your Pull request shortly ✨ 注意: 必须通过了 DNS-API-Test 才会被 review. 无论是修改, 还是新加的 dns api, 都必须确保通过这个测试.
As a result of PR #6111 updated the script to be a new dnsapi instead of replacing the older (but still working) version.
Changed to dns_openprovider_rest as suggested.
Pending new entry with anchor in /wiki/dnsapi2 once approved.
CC @TheLastProject @Ritbit @WinSCaP could you review and test?
Sorry, but I no longer work at the place I used to work where they used OpenProvider and don't have any domains with OpenProvider myself, so I have no domains I could possibly test this with anymore
As i did notice PR specs changed last couple of weeks and are more detailed.
Just added new entry to dnsapi2 to make the "checklist" complete for the PR.
https://github.com/acmesh-official/acme.sh/wiki/DNS-API-Test https://github.com/acmesh-official/acme.sh/wiki/DNS-API-Test https://github.com/acmesh-official/acme.sh/wiki/DNS-API-Test
@Neilpang yes, actions are enabled and the secrets also present with right values to allow tests to run.
Re-triggered the flow just by syncing the fork with current state, so it's pending workflow approval again. Initial run after the commit indicates an issue on the Docker clone/run;
the test should run in your repo: https://github.com/Lambiek12/acme.sh_openprovider_rest/actions/runs/13356270651
@Lambiek12 , what happened? Didn't the pull requestget accepted (or am I reading the git wrong)? I was waiting/hoping for your pull request to get added to the acme package.
@Lambiek12 , what happened? Didn't the pull requestget accepted (or am I reading the git wrong)? I was waiting/hoping for your pull request to get added to the acme package.
@RenevdBroek There will be a new PR soon..
I had issues from the start with the automation workflows not running on my fork. Since i had to reinstall some servers this weekend this came back into my focus as not finished 😞. Created new fork, now it looks to be running fine so should be coming soon 🤞