After our recent migration of our deployment server from tin to deploy1001 (T175288) there were reports from several users
about being blocked from deploying because files in their local repos still referred to the old deployment server name.
There were different categories of this issue, some were .config files in the "deployment-cache" directory which contained the string "tin.eqiad.wmnet". As the name implies these are cached files. One way to fix the issue was to manually edit the file and replace the host name. Another was apparently to just delete the file and have it recreated by scap and/or running scap with --refresh-config.
Seperate from this there was another category where .config files were not in the deployment-cache directory and still contained the old host name and it has been reported that this happened after a fresh OS install.
Also there were comments about a fix inside scap that is needed for this but still needs to be deployed.
This ticket is for all that and finding a clean way to handle this next time we have to switch from say deploy1001 to deploy1002.