While evaluating desec.io for my use case, I was surprised to find no mention of a potential terraform provider for desec.io.
I really appreciate the API-first approach. Taking this one step further in an infrastructure-as-code setup, a terraform provider seems like the way to go for reproducible and versionable zone management.
A generic Terraform provider would indeed be awesome. deSEC is a community effort, and several other integrations have been contributed by the community. Would you like to work on this? The ACME provider may give you some inspiration.
thanks for your reply, and thanks for this project! I saw the acme provider, but that of course only solves part of the problem of DNS in IaC
Would you like to work on this? The ACME provider may give you some inspiration.
I currently don’t have time for projects of that size, sadly. I’ll keep it in mind though, perhaps I can fund and mentor a student to do it some time. I imagine such a project can be based on the cloudflare terraform provider and shouldn’t be all that difficult to do.
I looked into this for a while, and I’m happy to report that I was able to build a working terraform provider for desec
It works fine so far. I implemented management of domains and rrsets, and added a reasonable level of documentation. It still needs acceptance tests before I could publish it in the terraform registry.
For the record, terraform compatibility is actually kind of rare outside of AWS/Azure/GCE/Cloudflare, and it was one of the must-have features I was looking for in a dns hoster. It’s only anecdotal, but for me that would have been a very effective hook in the “feature grid” on the front page.