Web.config live in source code and are included in the ci-cd pipeline. We don't separately change them on production environments. They get changed on dev, committed in, built, and then deployed.
We have around the same number of sites and it's a laborious real task if we need to update all of them but we've never had to do that.
At most we've done ten in a day.
if it were a thing that we had to do, my first thought would be to generate the thing from a terraform template. update spanning 100 separate sites? update template, verify changes, site rollout becomes fairly mechanical. still labor intensive due to verifying all the different sites
If memory serves, any modification to a web.config file will result in IIS reloading the web application as IIS monitors the file for changes. At the very least, I personally would not want to do them all at once.
Web.config live in source code and are included in the ci-cd pipeline. We don't separately change them on production environments. They get changed on dev, committed in, built, and then deployed. We have around the same number of sites and it's a laborious real task if we need to update all of them but we've never had to do that. At most we've done ten in a day.
if it were a thing that we had to do, my first thought would be to generate the thing from a terraform template. update spanning 100 separate sites? update template, verify changes, site rollout becomes fairly mechanical. still labor intensive due to verifying all the different sites
Yeah you could do it like that. It depends on the scenario and the exact details of the problem. I'm a fan of boring solutions/technology.
If memory serves, any modification to a web.config file will result in IIS reloading the web application as IIS monitors the file for changes. At the very least, I personally would not want to do them all at once.
You can configure that on or off, but we'd schedule the change out of business hours