feat: adds rudimentary script to import seantis risk excel.

[strfx]

Script to import our excel into RiskMatrix. Best used with new organizations to avoid conflicts.

Any idea how to handle conflicting risks?

Risks and assets (and therefore also assessments) are unique per organization, not catalog. Adding a risk from the excel that is already present in this organization will fail. Skipping them would result in an incomplete catalog. For now, I just abort the script.

misc:

• intentionally not listed openpyxl as dependency; import script is meant to be used internally, install as required
• added types-openpyxl to test requirements anyway to keep type checks

[Daverball]

@strfx Why not just assume that when a risk already exists, that it's the same risk and update it based on the import, rather than always adding one? You could add a little helper function get_or_create_risk, like you already do for assets. Alternatively you could rename either the existing or new risk to get rid of the conflict.

[strfx]

@Daverball that makes sense, thanks! I had the concept of catalogs wrong -- I assumed one excel ≈ one catalog. Will go the update-if-exists route 👍

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 102 lines in your changes are missing coverage. Please review.

Project coverage is 68.22%. Comparing base (4af0879) to head (314abd9).

Files	Patch %	Lines
...rc/riskmatrix/scripts/seantis_import_risk_excel.py	0.00%	102 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main       #5      +/-   ##
==========================================
- Coverage   70.92%   68.22%   -2.71%     
==========================================
  Files          61       62       +1     
  Lines        2573     2675     +102     
==========================================
  Hits         1825     1825              
- Misses        748      850     +102     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.