Closed Bug 1085409 Opened 10 years ago Closed 10 years ago

mediawiki-bugzilla extension uses soon-to-disappear BzAPI endpoint

Categories

(Websites :: wiki.mozilla.org, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
2014-Q4

People

(Reporter: gerv, Assigned: ckoehler)

Details

(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/1697] [dev=2014-10-23] [stage=2014-10-30] [prod=2014-11-06])

mediawiki-bugzilla is the biggest user of BzAPI at the moment. Here is a hit count for the past two weeks:

 282058 http://pear.php.net/package/http_request2) PHP/5.3.3
     16 http://pear.php.net/package/http_request2) PHP/5.5.9-1ubuntu4.4

It needs to migrate to the native REST API and/or the BzAPI-compatible shim in the next month, preferably much quicker.

This is upstream https://github.com/mozilla/mediawiki-bugzilla/issues/62 .

Here's the boilerplate letter:

Hi,

You are receiving this email because a service or services you are
believed to own or control is/are making requests of "BzAPI", the
Bugzilla API proxy server at https://api-dev.bugzilla.mozilla.org/.

This service is due to be decommissioned. Fortunately, Bugzilla has a
new native REST API which works somewhat similarly that you could use
instead:
https://wiki.mozilla.org/Bugzilla:REST_API

Moving to that new API would require some porting work. If that seems
like too much effort, fear not, because there is also a BzAPI
compatibility layer built on top of the new API. Because it's
compatible, using that should simply require a change of API endpoint.

Change:
https://api-dev.bugzilla.mozilla.org/latest/
(or https://api-dev.bugzilla.mozilla.org/1.3/)
to
https://bugzilla.mozilla.org/bzapi/

You should not expect the api-dev server to continue to work after
Friday 14th November. So please test and migrate your production
instance(s) over before then, either to the BzAPI compatibility endpoint
or to the new native REST API.

Thanks for using BzAPI. It's been a great ride :-)

Gerv
Assignee: nobody → gphemsley
OS: Linux → All
Hardware: x86 → All
For this we need to add (or replace) $wgBugzillaRESTURL in LocalSettings.php:

>>>
$wgBugzillaRESTURL = 'https://bugzilla.mozilla.org/bzapi';
<<<

That should be good enough for now, until the extension gets rewritten to use the REST API.
Assignee: gphemsley → nobody
Whiteboard: [dev=2014-10-23]
Whiteboard: [dev=2014-10-23] → [kanban:https://kanbanize.com/ctrl_board/4/1697] [dev=2014-10-23]
I've updated the extension to use the new end point:
https://github.com/mozilla/mediawiki-bugzilla/pull/63

(We're setting the API url directly in the extension rather than in LocalSettings.php.)
Changes not pushed to dev on Oct. 23rd since the pull has not yet been merged into the upstream repo.
(In reply to C. Liang [:cyliang] from comment #3)
> Changes not pushed to dev on Oct. 23rd since the pull has not yet been
> merged into the upstream repo.

Previously we've tested in dev before the pull request was approved. 

In any case, I can't figure out how to merge my own pull request so I'll look around for someone who can.
This is now merged:
https://github.com/mozilla/mediawiki-bugzilla/commit/a1e2d3ebc431f323d13f7ea3e80aaea21e61f816

Let's get this into dev asap so we can test and push to stage/dev. The current bugzilla endpoint is going away in a few weeks.
This change has been made and pushed out to dev.

$ cd /data/genericrhel6-dev/src/wiki-dev.allizom.org/wiki/extensions/Bugzilla
$ sudo git pull
remote: Counting objects: 4, done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 4 (delta 0), reused 1 (delta 0)
Unpacking objects: 100% (4/4), done.
From https://github.com/mozilla/mediawiki-bugzilla
   a2c6485..a1e2d3e  master     -> origin/master
Updating a2c6485..a1e2d3e
Fast-forward
 Bugzilla.php | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/1697] [dev=2014-10-23] → [kanban:https://kanbanize.com/ctrl_board/4/1697] [dev=2014-10-23] [stage=2014-10-30] [prod=2014-11-06]
This change has been pushed into stage.
Seems to be working fine on stage.
This change has been pushed to prod.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2014-Q4
Assignee: nobody → ckoehler
You need to log in before you can comment on or make changes to this bug.