immauss / immauss/openvas

Upgrade from mikesplain/openvas to immauss/openvas

Open
#274 7 comments 0 reactions 0 assignees View on GitHub
documentation enhancement good first issue help wanted
Dominant language
Shell
Stars
481
Forks
117
PR merge metrics
No merged PRs in 30d

Description

Dear immauss team

also like this Might not be the best topic for discussion

I plan to upgrade from mikesplain/openvas to immauss/openvas, but I noticed that mikesplain/openvas uses the sqlite3 database, while immauss/openvas uses the PostgreSQL database. The architecture between the two is also different, and currently, data can only be migrated through XML import and export. Is there a better way to achieve data migration?

Thanks Regards

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named. Start by reviewing the existing XML import and export migration path and comparing the SQLite and PostgreSQL data models; done would require an agreed migration approach that handles the architectural differences.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgresql, sqlite
Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.