789495 - Make it easier for TBPL contributors to test their changes on tbpl-dev without having to give out a static password

Status: RESOLVED WORKSFORME

(Tree Management Graveyard :: TBPL, defect)

Description

[Ed Morley [:emorley]]

At the moment tbpl-dev is behind htaccess auth, I'm presuming because it pulls on a 15 min cron directly from a user repo (which only needs level 1 access) and so could be at risk of abuse.

Many other mozilla foo-{dev,staging} types sites do not use this kind of auth - I'm presuming some perhaps because they require manual pushes even to dev/staging, or maybe because their repo requires level 3 access. 

An example: in the case of self-serve, there is only the standard level 1 LDAP access required to access the live instance, but yet no push to production is required - the changes I landed in bug 786290 went straight to prod! (This may just be an oversight I guess).

Either way, it would be helpful if we didn't have to hide tbpl-dev behind a login.

Perhaps we can do bug 772546 & make the new repo require level 2/3. Would that be sufficient? Not sure who in IT can advise on policy for this...

Comment 1

[Ed Morley [:emorley]]

HTTP auth disappeared at some point - don't know when or why, but not complaining :-)
(The repo is level 3 access now so not needed).

Comment 2

[Ed Morley [:emorley]]

(Have updated https://intranet.mozilla.org/Websites/Stage_Passwords#TBPL)