Update terraform sdk to v2

[selfuryon]

How about updating terraform sdk (and maybe other packages) to v2 version?

Can do it in future PRs

[mbag]

Hi @selfuryon yes, this is something we should definitively do. I would however, like to migrte the outstanding PRs so that we avoid potential conflicts with the new SDK.

[selfuryon]

Yeah, I'm going to make separate PR for that.
How about migrate communication with PowerDNS to separate go-binding library for PowerDNS (need to create it) for separating logic of communication with powerdns and provider logic?

[mbag]

How about migrate communication with PowerDNS to separate go-binding library for PowerDNS (need to create it) for separating logic of communication with powerdns and provider logic?

After adopting this provider, we were looking for go library that would do that. I know there are mutliple libraries out there doing this. However, we didn't find anything that was maintained actively, but most important we didn't find lirbary that would be officially promoted/endorsed by core PowerDNS team. As you might have noticed, this provider, is not created/maintained by the comapny doing development on the core PowerDNS.

I don't mind using third party PowerDNS library, but we use subset of the PowerDNS API features. It would be an overkill to maintain such client, that would have general usability outside of this provider @splashx what are your thoughts on this?

[selfuryon]

In our company we want to manage our PowerDNS servers completely through terraform, so I want to create implementation for almost all aspect of API endpoints for auth/recursor PowerDNS servers.
For this task I thought to create simple go-bindings, it will be really much simpler to add functionality via such approach.

[jbe-dw]

I used go-swagger to create our PowerDNS Admin provider, but I really don't like the generated code. It uses the publicly available swagger API definition to create a ready to use client (any language, including go). All naming relies on the api itself. It works if the API matches the swagger yaml.

Rewriting the bindings is a long way to go, unless you're not alone and have full time to do so.

I have talked to PDNS team and the API is a plus, not the cornerstone of their software, so they won't spend time on it. I would have said that they have a master card to play about automation to sip Bind customers which does not offer any API and automation at all (or poorly). If I was their lead I would have invest efforts to deliver tooling around automation topics.

[mmianl]

In case someone stumbles across this issue: I forked this repo and upgraded to v2 here. This repo doesn't appear to be maintained anymore, am I right @mbag @jbe-dw ?

[jbe-dw]

I have a new job now and I left power dns quite some time ago, but I'd say it looks like it. Le ven. 23 mai 2025, 14:37, mmianl ***@***.***> a écrit :

…

*mmianl* left a comment (pan-net/terraform-provider-powerdns#84) <#84 (comment)> In case someone stumbles across this issue: I forked this repo and upgraded to v2 here <https://github.com/mmianl/terraform-provider-powerdns>. This repo doesn't appear to be maintained anymore, am I right @mbag <https://github.com/mbag> @jbe-dw <https://github.com/jbe-dw> ? — Reply to this email directly, view it on GitHub <#84 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMCQ5BNZ2LZ7QPDIBLPH673274JCDAVCNFSM6AAAAAB5YUS5GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBUGI4DKMJVHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>