Add scan-config-json type#357
Conversation
Conventional Commits Report😢 No conventional commits found. 👉 Learn more about the conventional commits usage at Greenbone. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #357 +/- ##
=======================================
Coverage 99.36% 99.36%
=======================================
Files 7 7
Lines 470 472 +2
=======================================
+ Hits 467 469 +2
Misses 3 3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
215d11f to
ab0da39
Compare
bjoernricks
left a comment
There was a problem hiding this comment.
As this is an enterprise only feature as the jsons are not available for the community, I just want to be sure that this command is optional and not run when calling greenbone-feed-sync without arguments?
Yes, that is the intention. The new |
What
Add a dedicated
scan-config-json/scan-config-jsonsfeed sync type and related URL/destination settings.Why
OPENVAS DETECT/OEM customers need scan configs as JSON, but these files should be synced only when explicitly requested.
References
DEVOPS-2126
Checklist
validated with parser/config unit tests, running Ruff and black.