Bug #17488
Add confirmation step to db:import task
Team Backlog:
Fixed in Releases:
Found in Releases:
Description
The task could wipe the existing database, so I think it's sensible to ask twice in case the job was run by accident or the user didn't know that would happen.
Related issues
Associated revisions
Fixes #17488 - Add confirmation to import db task
(cherry picked from commit c0cd333a24b90c6acd93c245a3ee96f941f32bea)
History
#1
Updated by Daniel Lobato Garcia over 2 years ago
Updated by - Related to Bug #17474: db:import_dump does not clean existing database prior to re-importing added
#2
Updated by The Foreman Bot over 2 years ago
Updated by - Status changed from New to Ready For Testing
- Assignee set to Daniel Lobato Garcia
- Pull request https://github.com/theforeman/foreman/pull/4055 added
#3
Updated by Anonymous over 2 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset c0cd333a24b90c6acd93c245a3ee96f941f32bea.
#4
Updated by Dominic Cleal over 2 years ago
Updated by - Legacy Backlogs Release (now unused) set to 189
#5
Updated by Daniel Lobato Garcia over 2 years ago
- Target version set to 1.4.3
Fixes #17488 - Add confirmation to import db task