[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):

 Meejah: could you please post your comments about "get off Trac" on the
 correct issue: either #4095 for the requirement (where self-hosting was
 explicitly not excluded) or #4161 for the execution.

 This issue is about "Infrastructure as Code to manage DNS configurations"
 which, in my opinion, could be really helpful for many issues.

 My apologies if it was not clear in the above comments, but this issue is
 not proposing "the addition of self-hosted/managed DNS". The DNS zone is
 already managed by Gandi and since we've concluded that delegating its
 management programmatically with a token was unfeasible (at the moment),
 the proposal it to have the zone managed  by Hetzner instead.

 The goal here (and in #4095) is rather to decrease the burden: it is not
 adding anything new, but just making what's already there easier to
 manage.

 Meejah: could you please attach an export of the DNS zone tahoe-lafs.org
 currently hosted by Gandi?

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