627697 - Ability to enable/disable extensions from the web UI

Status: NEW

(Bugzilla :: Administration, task, P2)

Description

[rojanu]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:2.0b9) Gecko/20100101 Firefox/4.0b9
Build Identifier: 

A tool to manage extensions would be very nice

- Enable/Disable extensions
- Apply patches within extension folder
   To apply patches
   * Extensions should contain supported/for Bugzilla versions
   * Patch names should be in certain structure, 
          ExtensionName-BugzillaVersion.patch e.g. Foo-4.1.13.patch

Reproducible: Always

Comment 1

[Max Kanat-Alexander]

Well, I don't think we'd want the webserver to be able to patch extensions. But having a web UI to enable/disable extensions is something we could do. However, note that enabling many extensions requires running checksetup.pl, which is not something that the webserver can do.

Comment 2

[rojanu]

I was thinking having two different Front Ends for the tool;

1- Available via web UI, which would only manage extension that doesn't require checksetup.pl to run
2- A pl to run on command, which could enable all extensions and is able to patch 

Alternatively,
checksetup.pl could check and list all extensions including extensions patch status.  This would be very useful, I am hoping that with new extension structure people would write more extensions and an admin should be able to tell the statuses of all extension without checking all extensions directories

* This is Bugzilla x.x.x on perl x.x.x
* Running on .....................

Checking perl modules...
....

Checking available perl DBD modules...
....

The following Perl modules are optional:
...
Reading ./localconfig...
...
Checking  Bugzilla Extensions
Name            Status              Patched
HelloWorld      Disabled            No
Foo             Enabled             Yes
Test            Enabled             No

Removing existing compiled templates...
Precompiling templates...done.
Fixing file permissions...

Comment 3

[Max Kanat-Alexander]

Well, it's possible that we could have a web UI that could fix permissions and do all of the checksetup-related activities that an extension does. After all, there are only a few hooks that checksetup runs--we could perhaps just run those hooks from the extension directly, although that is a bit sketchy architecturally.

Comment 4

[Frédéric Buclin]

We are going to branch for Bugzilla 4.4 next week and this bug is too invasive or too risky to be accepted for 4.4 at this point. The target milestone is set to 5.0 which is our next major release.

I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else on time for 5.0.