Closed
Bug 1354130
Opened 7 years ago
Closed 7 years ago
stop exporting scheduled changes in production dump
Categories
(Release Engineering Graveyard :: Applications: Balrog (backend), enhancement, P2)
Release Engineering Graveyard
Applications: Balrog (backend)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: anjul.ten)
References
Details
(Whiteboard: [lang=python][ready][good first bug])
For a couple of reasons: 1) They don't work, because we don't export permissions. When the Agent tries to enact them locally, they will fail because the user that created them doesn't have permission to make the change. 2) Even if we made them work, it would be confusing to have a freshly brought up database change itself. I think we just need to remove them from the list here: https://github.com/mozilla/balrog/blob/master/scripts/manage-db.py#L128
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → anjul.ten
Comment 1•7 years ago
|
||
Commit pushed to master at https://github.com/mozilla/balrog https://github.com/mozilla/balrog/commit/cb63e88011a1aa2954ae94cd336b9103d392c90f Bug 1354130: Stop exporting scheduled changes in the production dump. (#302). r=bhearsum
Assignee | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Product: Release Engineering → Release Engineering Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•