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

 During the last N&B (13th of May), Meejah said that:

 - he was too busy to answer the related requests in Trac (or by email),
 - he is unsure if he can export the content of the zone or change the name
 servers,
 - he is only knows that he can change A and AAAA records.

 But he also clearly stated he will not do the changes described above w/o
 an explicit approval from Brian.

 Recap:

 - only Brain and Meejah can manage the DNS, and Meejah only partly
 - the initial ask for a token to read/write DNS records at Gandi could not
 be achieved w/o direct involvement of Brian.
 - the workaround to host the zone elsewhere might be possible, assuming
 Meejah has the privileges, but he will not do it w/o approval from Brian
 anyway.

 I still hope Meejah will upload the content of the zone, so we have a copy
 of those data somewhere, and/or commenting on why he could/would not do it
 (there should not be any secrets in there IMO).

 Meanwhile, I've created a new PR to manage only a sub-zone which should
 allow us to achieve the goals described above, albeit only for new
 services:

 - [https://github.com/tahoe-lafs/infrastructure/pull/57 Manage a sub zone
 of.tahoe-lafs.org with OpenTofu infrastructure#57]

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