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

 Can you describe what all these complex / real-time DNS changes are for?

 I was imaging that any transition plan would look a lot more like: 1. set
 up new thing; 2. point DNS at new thing.

 What's the best spot right now for an overview: pros, cons, alternatives
 etc? (Both so I know the right thing to look at, and for anyone reading
 this)

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