Since wdqs-updater is used outside WMF, we should ensure that those external use cases can be identified more easily. At the moment, the user agent is hardcoded, it should be a configuration argument instead.
Note that this concern was surfaced during the investigation of T217893.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| wdqs-updater: make user agent configurable from http.userAgent system property | wikidata/query/rdf | master | +76 -3 |
Blazegraph accepts http.userAgent but looks like Updater does not. Probably makes sense to make it do the same.
Change 495863 had a related patch set uploaded (by Gehel; owner: Gehel):
[wikidata/query/rdf@master] wdqs-updater: make user agent configurable from http.userAgent system property
Change 495863 merged by jenkins-bot:
[wikidata/query/rdf@master] wdqs-updater: make user agent configurable from http.userAgent system property