feat: migrate Vulnerability Management API from v1beta1 to v1#46
Merged
feat: migrate Vulnerability Management API from v1beta1 to v1#46
Conversation
- Update all three endpoint paths to /secure/vulnerability/v1/... - Runtime: rename policyEvaluationsResult -> policyEvaluationResult, add resourceId field - Pipeline: rename policyEvaluationsResult -> policyEvaluationResult, rename mainAssetName -> pullString - Registry: rename mainAssetName -> pullString - Add tests validating v1 response field mapping for all three components - Add test asserting endpoint paths no longer reference v1beta1 Changes verified against live v1 API responses.
tembleking
approved these changes
Feb 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Migrates all Vulnerability Management API endpoints from the deprecated
v1beta1version tov1.runtime-results,registry-results,pipeline-results) from/secure/vulnerability/v1beta1/...to/secure/vulnerability/v1/...policyEvaluationsResult→policyEvaluationResult(field renamed in v1); added newresourceIdfield to typepolicyEvaluationsResult→policyEvaluationResult;mainAssetName→pullString(field renamed in v1)mainAssetName→pullString(field renamed in v1)The
mainAssetName→pullStringchanges for pipeline and registry were discovered by comparing against live v1 API responses, as these endpoints are not covered in the official migration spec.Test plan
policyEvaluationResult,pullString)SysdigApiClient.test.tsasserting endpoint paths use/v1/and notv1beta1policyEvaluationResultfiltering behaviour in runtime and pipeline