Closed
Bug 1035431
Opened 10 years ago
Closed 10 years ago
Chief access for badges.mozilla.org devs
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: andrew, Unassigned)
Details
(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/502] )
Erik (:echristensen) and I are taking over the development of badges.mozilla.org. For the time being, we'll need access to (I think):
http://genericadm.private.phx1.mozilla.com/chief/badgus.prod
http://genericadm.private.phx1.mozilla.com/chief/badgus.stage
Our LDAP accounts are:
- andrew@mozillafoundation.org
- erik@mozillafoundation.org
Thanks,
- Andrew
Comment 1•10 years ago
|
||
Still meaning to get around to the pull request that's pending, but I think I can resolve this request pretty quickly in private email. That is, if the credentials I have still work.
Let's see...
Comment 2•10 years ago
|
||
Just sent email, give things a try. If it works, go ahead and mark this bug resolved & verified. Otherwise, we'll need someone with access to reset the passwords.
Comment 3•10 years ago
|
||
:lorchard is on the right track here. you can access the chief instance on genericadm as long as you're connected to a mozilla vpn. to push, you simple need the password Les sent you.
i am going to mark this bug as r/wontfix since there's not action here for our team. however, if you're having any issues with your deployment, please feel free to reopen this bug and/or reach out to me.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•