Migrate vulnerability accepted-risks API from v1beta1 to v1

[tembleking]

Summary

The vulnerability accepted-risks endpoints currently use the deprecated /v1beta1 API version, which is scheduled for removal in February 2026. We need to migrate to the /v1 API before the deprecation deadline.

Current State

The following endpoints in sysdig/internal/client/v2/vulnerability_accept_risk.go use the deprecated v1beta1 API:

• POST /secure/vulnerability/v1beta1/accepted-risks (create)
• GET /secure/vulnerability/v1beta1/accepted-risks/{id} (get)
• PUT /secure/vulnerability/v1beta1/accepted-risks/{id} (update)
• DELETE /secure/vulnerability/v1beta1/accepted-risks/{id} (delete)

Required Changes

1. Update all endpoint paths from /v1beta1/ to /v1/
2. Verify any request/response schema changes between API versions
3. Update tests accordingly
4. Test against the v1 API endpoints

Priority

High - The v1beta1 APIs are being phased out and will be removed in February 2026.

References

• File: sysdig/internal/client/v2/vulnerability_accept_risk.go

[airadier]

Please note AFAIK the Risk Acceptance API does not exist in V1 and I am not aware of plans to release a v1 for now.

I think you mean the vulnerability management (pipeline, registry, runtime results and fetch full scan result)?

[tembleking]

It does not, closing this since it does not exist for v1, we can still support v1beta1 because the deprecation notice will be required for several months before removing it.