273579 - read only Bugzilla database

Status: RESOLVED WONTFIX

(Bugzilla :: Administration, task)

Description

[Matthias Thullner]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: 

unfortunatly my department decided to migrate from Bugzilla to ClearQuest :-(

I am looking for a way to keep Bugzilla alive after migration, but without the 
possibility to edit/submit new bugs.

The only possibility I could think of so far is to remove the necessary scripts 
like:
- enter_bug.cgi
- process_bug.cgi
- attachment.cgi
- createaccount.cgi
- votes.cgi
- edit*.cgi
...

But if we switch back to Bugzilla (e.g. ClearQuest is not working propperly :-)
I would prefer a simplier way to switch from read-only to normal function.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.



Expected Results:  
easy way to set Bugzilla to read only, i.e. no editing is possible

I know this is not really a bug, but a request. But I did not know where to 
address this.

Bugzilla version is: 2.16

Comment 1

[Dave Miller [:justdave]]

(In reply to comment #0)
> unfortunatly my department decided to migrate from Bugzilla to ClearQuest :-(

Ewww, of all the things to choose to move to...  I do feel sorry for you. 
Although to be fair, it's been a few years since I've seen ClearQuest, and maybe
they've cleaned up their act some.  I know we have in that time, too ;)

Best short-term thing I can suggest it to change the permissions of the bugs
user in the MySQL database...  i.e. remove the insert/update/delete privileges
for everything except the logincookies tables.  If you remove those privileges
for the  logincookies table, then you'll need to make sure everything is
readable without logging in, because no one will be able to.

I think this is a valid feature request for Bugzilla itself, but leaving it
unconfirmed for the moment since I think I've seen it before, so this might be a
dupe.

Comment 2

[Dave Miller [:justdave]]

OK, found what I thought was going to be the dupe for this.  It's not exactly
the same, but this would be a logical follow-on to it, so setting a dependency
on it.  The other bug is to use multiple read-only mirrors that forward you to
the master when you need to change something.  Once that works, it would be a
simple matter of throwing a switch that says there is no such master, so writes
can't happen.

Comment 3

[Gervase Markham [:gerv]]

Only one person has ever asked for this, and it would be difficult to make sure all bases were covered, so I propose WONTFIX.

Gerv