Quarry has had minimal attention from cloud-services-team for some time, and we are changing that now. One thing to look at is just a basic set of improvements and upgrades to the operational layout including CI, server upgrades and possibly database changes.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T288982 Productionize quarry a bit | |||
| Resolved | • rook | T288976 Add black formatting to quarry linter | |||
| Resolved | • rook | T288528 quarry to python 3.7 | |||
| Resolved | Andrew | T210359 Develop Quarry tests | |||
| Resolved | Andrew | T210360 Setup tests framework | |||
| Declined | None | T289531 Switch to using prefix puppet instead of direct-on-instance puppet | |||
| Duplicate | None | T290184 Should quarry use our standard secrets management | |||
| Resolved | • rook | T291204 make automatically deploy-able staging quarry |
Event Timeline
Comment Actions
When, where, who and how should we decide what goes here? (has that been done already? might have missed it.)