Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Enhancement] Copy the database even if the schema version doesn't match (with force flag) #2105

Closed
To-om opened this issue Jun 30, 2021 · 0 comments
Closed

[Enhancement] Copy the database even if the schema version doesn't match (with force flag) #2105

To-om opened this issue Jun 30, 2021 · 0 comments
Labels
feature request TheHive4 TheHive4 related issues
Milestone
4.1.7

Comments

@To-om
Copy link
Contributor

To-om commented Jun 30, 2021

Request Type

Enhancement

Feature Description

If the version of schema differs with the expected version in the cloner tool, the copy won't start.The aim of this issue is to add a parameter to force the copy even if the version mismatch. This parameter must be used carefully because the source data can be incompatible with the target schema and make a inconsistent data (that can't be fixed). A schema and data integrity check should be run manually after the copy.
@To-om To-om added feature request TheHive4 TheHive4 related issues labels Jun 30, 2021
@To-om To-om added this to the 4.1.7 milestone Jun 30, 2021
To-om added a commit that referenced this issue Jun 30, 2021
@To-om
#2105 Add force parameter in database cloner tool
75d6ff7
To-om added a commit that referenced this issue Jul 1, 2021
@To-om
#2105 Fix injection of case number actor
eb1bee3
@To-om To-om closed this as completed Jul 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request TheHive4 TheHive4 related issues
Projects
None yet
Milestone
4.1.7
Development

No branches or pull requests
1 participant
@To-om