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

 I have explained many months ago that I'm fine with adding an A or AAAA
 record or two (via "click ops" in my Gandi account), but I don't believe I
 can create a token for just the delegated access I have for tahoe-lafs.org
 and will of course not be giving a token for my Gandi account, which
 controls many other domains.

 Nobody has asked me add such records. I was told you were talking to Brian
 about this.

 (My understanding of the wider "migration" piece was that the next step
 was to weigh pros / cons of another self-hosted situation vs. cloud-hosted
 services. I'm not privy to any discussion that may have happened with
 Brian or others outside N&B and this tracker though)

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