Closed
Bug 1335109
Opened 9 years ago
Closed 9 years ago
Store the list of available emr releases in a database table
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mdoglio, Unassigned)
References
Details
At the moment users need to wait for the next atmo release to try a new emr version in the best case. Someone also needs to write a patch and generate a new db migration. We could instead create a new db model with its counterpart in the admin site. That would make adding/removing a emr release as easy as clicking a button.
|
||
Comment 1•9 years ago
|
||
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
|
||
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•