-
Notifications
You must be signed in to change notification settings - Fork 668
Vulnerabilities and vulnerability exports API #2316
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
Comments
Hi @srisaravananwt, thanks for the report. I've added the |
@nejch Thanks. Could you please point me to the similar MR for any other features like this? I will try to contribute. |
Awesome! Since vulnerabilities is mostly an instance-level endpoint, (e.g. you will likely do Now I see it has a lot of custom endpoints for confirm, dismiss, etc. These will be methods on the object itself, not the manager (e.g. Also keep in mind I just noticed they are deprecating this REST endpoint in favor of GraphQL. But that will probably take years, so if you need it now it probably makes sense still :) |
Hey @srisaravananwt , any work on this? I need this as well and can help out on the fork. |
@Rewdog I have used GraphQL to export the vulnerability report. |
I think this is the only way forward, the REST APIs (Vulnerabilities and Vulnerability Findings) are deprecated and have issues (i.e., pagination doesn't currently work). That said, pagination is also currently broken in the GraphQL securityReportFindings connection. I'm currently working with their tech support to figure it out. |
Description of the problem, including code/CLI snippet
Need modules for https://docs.gitlab.com/ee/api/vulnerabilities.html and https://docs.gitlab.com/ee/api/vulnerability_exports.html
Expected Behavior
Option to use Vulerabilities and vulnerability_export api.
Actual Behavior
No option to use Vulerabilities and vulnerability_export api.
Specifications
The text was updated successfully, but these errors were encountered: