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.

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

Fix and simplify SecInfo migration #1331

Merged
merged 3 commits into from
Oct 21, 2020

Conversation

timopollmeier
Copy link
Member

@timopollmeier timopollmeier commented Oct 21, 2020

What:
This fixes the feed type check in gvm_migrate_secinfo and simplifies the migration by always re-initializing and re-syncing the SCAP and CERT databases to get them to a new version.

Why:
To ensure the migration works and to keep future SCAP and CERT migrations simple.

How:
Tested by modifying the value for database_version in the SCAP and/or CERT schema meta table to versions larger or smaller than the supported versions and running gvmd and gvmd --migrate.
Larger version numbers should be rejected while smaller ones will make gvmd rebuild the database.

Checklist:

The check must fail for both possible types not just one for the type
to be invalid.
To simplify the SCAP and CERT database migration, the databases are
fully reinitialized and synced again if gvmd requires a newer version.
@timopollmeier timopollmeier marked this pull request as ready for review October 21, 2020 07:31
@mattmundell mattmundell merged commit 3a61f4d into greenbone:master Oct 21, 2020
@timopollmeier timopollmeier deleted the secinfo-migration branch October 15, 2021 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants