[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4162: Infrastructure as Code to manage DNS configurations

[Tahoe-LAFS]

#4162: Infrastructure as Code to manage DNS configurations
------------------------------------+-----------------------
     Reporter:  btlogy              |      Owner:
         Type:  enhancement         |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  n/a
   Resolution:                      |   Keywords:  IaC
Launchpad Bug:                      |
------------------------------------+-----------------------

Comment (by btlogy):

 With now more than 6 weeks (and counting) required to update of the DNS
 records via #4183 seem to confirm my initial idea that using the
 Infrastructure as Code to manage the whole `tahoe-lafs.org` domain was
 required to MoveOffTrac (as requested in #4161).

 To that purpose, I've reworked an existing draft PR and created a new one
 to eventually move forward with this improvement in the future:

 - Manage all records in tahoe-lafs.org zone on Hetzner with Tofu
 [https://github.com/tahoe-lafs/infrastructure/pull/62 infrastructure#62]
 - Switch from Hetzner to deSec as DNS hosting provider [https://github.com
 /tahoe-lafs/infrastructure/pull/83 infrastructure#83]

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4162#comment:29>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage