Closed
Bug 1558846
Opened 5 years ago
Closed 5 years ago
Stage db access in gcp for wlach
Categories
(Cloud Services :: Iodide, task, P1)
Cloud Services
Iodide
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: wlach, Assigned: robotblake)
Details
(Whiteboard: [DataOps])
Issues like https://github.com/iodide-project/iodide/issues/1930 may require some manual db cleanup after the issue itself is resolved. To help self-serve solutions, it would be helpful if I had direct access to the db instance we have running in gcp.
Flags: needinfo?(bimsland)
|
Assignee | |
Updated•5 years ago
|
Assignee: nobody → bimsland
Flags: needinfo?(bimsland)
Priority: -- → P1
|
|
Assignee | |
Comment 1•5 years ago
|
||
:wlach confirmed he was able to access the database, just waiting on confirmation that he's able to do the needed cleanup.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Updated•5 years ago
|
Whiteboard: [DataOps]
|
|
Assignee | |
Comment 2•5 years ago
|
||
Whoops, didn't mean to close it.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
|
Reporter | |
Comment 3•5 years ago
|
||
Yup, thanks Blake! All avatar urls should now be https on the stage server.
Status: REOPENED → RESOLVED
Closed: 5 years ago → 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•