Running scap update-interwiki-cache in mwdeploy2002 changes the interwiki file but doesn't make the patch nor deploys it. IIRC it used to do that.
Description
Details
Related Objects
Event Timeline
Thanks for the pointer but this is adding a lot of toil to an already miserable process of creating new wikis. See one, two and three (specially T158730#5527658). We don't need to revert to the previous way though. We can add it the file to gitignore, show diff and then sync the file. If history of that file is important, we can add a local git submodule, commit it and then after showing diff, sync it. Or any other idea that removes toil from this process.
cc @Krinkle @Zabe @Urbanecm and @thcipriani
@Ladsgroup How hard would it be to run the script to create the updated interwiki map locally instead of in prod? If feasible, it could be automated as part of the creationg one of the wmf-config commits that you need regardless as part of wiki creation.
Then it becomes a normal scap deploy after that.
It relies on realms to build a different interwiki file depending on whether it's production or beta: https://gerrit.wikimedia.org/g/mediawiki/extensions/WikimediaMaintenance/+/c8675aff88719eedb14e9f87ca2ceef31ee72287/dumpInterwiki.php#87
Otherwise, it looks doable judging by the code
Change 975356 had a related patch set uploaded (by Krinkle; author: Krinkle):
[mediawiki/extensions/WikimediaMaintenance@master] dumpInterwiki: Add --target-realm and --mwconfig-dir to ease local usage
Change 975356 merged by jenkins-bot:
[mediawiki/extensions/WikimediaMaintenance@master] dumpInterwiki: Add --target-realm and --mwconfig-dir to ease local usage