api: added migration to avoid horusec id in stored vuln hashes #389
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.
Signed-off-by: Nathan Martins [email protected]
- What I did
Pr ZupIT/horusec#636 of the CLI introduced a bug that changed all hashes of the Horusec engine and all the vulnerabilities that went to the manager were updated and identified as new, losing the changes made. This pull request comes with a migration to change the hashes to the old standard and avoid breaking pipelines that were correct. CLI fix can be found in pr ZupIT/horusec#678.
- How to verify it
- Description for the changelog