Local repository is configured in $wgWBClientSettings using settgings: repoDatabase, entityNamespaces, repoConceptBaseUri, whereas foreign repositories are conigured using array setting "foreignRepositories". Those should be unified to a single "repositories" setting (local repo being empty-string repository there).
Description
Details
Event Timeline
Change 400239 had a related patch set uploaded (by Ladsgroup; owner: Amir Sarabadani):
[mediawiki/extensions/Wikibase@master] Rename foreignRepositories config in client to repositories
Change 400415 had a related patch set uploaded (by Ladsgroup; owner: Amir Sarabadani):
[mediawiki/extensions/Wikibase@master] Use foreignRepositories settings in clients instead of repoXXX
Change 402386 had a related patch set uploaded (by WMDE-leszek; owner: WMDE-leszek):
[mediawiki/extensions/Wikibase@master] [WIP] Integrate repository configuration of WikibaseRepo into single setting
Change 400239 abandoned by Ladsgroup:
Rename foreignRepositories config in client to repositories
Reason:
Merged into other patches
Please ignore my previous comment on also integrating Repo component's settings into a single "repositories" setting. Does not seem thought-through. Definitely something to be left out for now. So this is only about the Client's settings.
Change 402386 abandoned by WMDE-leszek:
[WIP] Integrate repository configuration of WikibaseRepo into single setting
Change 400415 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] Integrate all Client's repository settings into a single setting
Change 404679 had a related patch set uploaded (by WMDE-leszek; owner: Amir Sarabadani):
[mediawiki/extensions/Wikibase@master] Integrate all Client's repository settings into a single setting
Change 404679 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] Integrate all Client's repository settings into a single setting
@Ladsgroup, should this deprecation be part of acceptance criteria for this ticket? My gut feeling says yes, it should. What's missing to do this?
Things need to be done:
- Deprecated repoUrl and move it to repository definitions, how? I have absolutely no idea.
- Communicate about this deprecation.
- Change configs in beta and prod (I tried once and failed miserably)
- Remove the old config
I think it would be good to seperate them into several tickets so we don't drag it from sprint to sprint. The first and third point already have tickets.
I don't think moving repoUrl (and other stuff, like repoScriptPath, repoArticlePath) is critical. It was meant as part of this task indeed. I am going to make this ticket explicitly for unifying settings to repositories, and create a new repoXXX ticket. It does not need to be worked on right away IMO, though.