Fix secrets integration tests after AM v1.7.0

jfrog / jfrog-vscode-extension

JFrog VS-Code Extension

https://jfrog.github.io/jfrog-vscode-extension

Apache License 2.0

189 stars 32 forks source link

Fix secrets integration tests after AM v1.7.0 #476

Closed attiasas closed 1 month ago

attiasas commented 1 month ago

[x] All tests passed. If this feature is not already covered by the tests, I added new tests.
[x] I used npm run format for formatting the code before submitting the pull request.

In AnalyzerManager v1.7.0+ the name of the rule-id of an expected secret scan issue was changed. source -> REQ.SECRET.GENERIC.CODE Breaking the test. changing to new value

github-actions[bot] commented 1 month ago

[![👍 Frogbot scanned this pull request and did not find any new security issues.](https://raw.githubusercontent.com/jfrog/frogbot/master/resources/v2/noVulnerabilityBannerPR.png)](https://docs.jfrog-applications.jfrog.io/jfrog-applications/frogbot)

[🐸 JFrog Frogbot](https://docs.jfrog-applications.jfrog.io/jfrog-applications/frogbot)

jfrog / jfrog-vscode-extension

Fix secrets integration tests after AM v1.7.0 #476

[x] I used npm run format for formatting the code before submitting the pull request.

[x] I used `npm run format` for formatting the code before submitting the pull request.