Closed
Bug 1527698
Opened 6 years ago
Closed 6 years ago
copy production database to staging and testing environment for shipit/api project
Categories
(Cloud Services :: Operations: Miscellaneous, task)
Cloud Services
Operations: Miscellaneous
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: garbas, Assigned: oremj)
Details
there is no sensitive data in the database so no cleanup is needed.
this is needed to be as close as possible to production before trying to compare product details from staging.
Assignee | ||
Comment 1•6 years ago
•
|
||
Is this a one-off request or should it be ongoing?
If it's an ongoing request, how do you want to orchestrate it? During the import, the staging and testing environments will essentially be down, so we'll need to plan when this should happen and how often, so testing against staging/testing won't return unexpected results.
Assignee | ||
Updated•6 years ago
|
Flags: needinfo?(rgarbas)
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → oremj
Reporter | ||
Comment 2•6 years ago
|
||
:oremj we would only need to do this on certain occasions for now. i don't think we need to orchestrate this
Flags: needinfo?(rgarbas)
Assignee | ||
Comment 3•6 years ago
|
||
testing and staging instances have been updated with a copy of the production database.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•