Closed
Bug 1454014
Opened 7 years ago
Closed 7 years ago
more release_repositories table to django-land
Categories
(Socorro :: Webapp, task, P1)
Socorro
Webapp
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: willkg, Assigned: willkg)
References
Details
We're in the process of moving "ownership" of Postgres things to the webapp. Bug #1452909 requires that we add an item to the release_repositories table. With the old infrastructure, I could do that from the admin node--no big deal. With the new infrastructure, I can't do it at all.
Further, we should probably figure out a way to do this sort of thing more easily since we've got other lookup tables in similar situations even if there's no immediate need to adjust them.
This bug covers looking into moving the ownership of the release_repositories table from alembic/sqlalchemy to the webapp.
Assignee | ||
Comment 1•7 years ago
|
||
Making this a P1 to figure out soon and grabbing it.
Assignee: nobody → willkg
Priority: -- → P1
Assignee | ||
Comment 2•7 years ago
|
||
I looked into it more and this specific table is used in the product versions flow which is likely to change soon, so it seems like a bad candidate to use.
Given that, I'm going to WONTFIX this.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•