Closed Bug 1310232 Opened 8 years ago Closed 8 years ago

double check that Signoffs were made when making changes to tables that require them

Categories

(Release Engineering Graveyard :: Applications: Balrog (backend), defect)

Product:
Release Engineering Graveyard
Component:
Applications: Balrog (backend)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1310210

People

(Reporter: bhearsum, Assigned: bhearsum)

References

Details

As a safeguard measure, we should implement a secondary check for Required Signoffs at a very low level. Ideally, this would happen is AUSTable's delete, update, and insert methods. They should be able to check whether or not the table has required signoffs, and if so, whether or not they've been met. Doing this secondary check here has a couple of benefits: - It should help us prevent bustage in the future if the Required Signoffs or other tables are refactored. - It protects us against a bug in the Balrog Agent requesting that a change be enacted before all Signoffs have been done.
Depends on: 1310209
Depends on: 1310210, 1310218
Blocks: 1278974
Turns out I'm doing this as part of bug 1310210.
Assignee: nobody → bhearsum
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Product: Release Engineering → Release Engineering Graveyard
You need to log in before you can comment on or make changes to this bug.