This is because the whole idea is that you have inaccessible, locked down Production servers that only Puppet (which is driven from a central, governed configuration management source) has authority to configure i.e. no SSH and no root access.
Thus leaving the only option being to physically visit each server at the datacenter and issue the commands.
[1] https://www.puppet.com/docs/puppet/5.5/ssl_regenerate_certif...
Which if we assume only a team of your size remains then it would take 300+ days.
That would mean no OS patches etc which would put them firmly in the crosshairs of the FTC.
[1] https://twitter.com/d_feldman/status/1562265193249390593
If it's not the case then Twitter is definitely in far more trouble because according to past engineers at least a few of their services needed manual intervention on a full scale reboot. And losing quorum in a distributed system is never pretty.
Anecdotal point of data: infosec.exchange hosts 30k users on 7 servers (https://infosec.exchange/@jerry/109374478717918484). That's a 1:5 ratio. Again, not the same usage and performance requirements, but I find it interesting.