We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As part of the migration plans to new Checkmarx, we need to adapt our components' security-scanner-configs to be picked up by new Cx mechanisms.
To be added:
kind: kcp / kyma //depending on where the component is deployed checkmarxOne: checkmarx_preset_golang
For lifecycle-manager and modulectl kind value of kcp should be used, for runtime-watcher and template-operator kind is kyma.
kcp
kyma
Security compliance
No response
The text was updated successfully, but these errors were encountered:
nesmabadr
No branches or pull requests
Description
As part of the migration plans to new Checkmarx, we need to adapt our components' security-scanner-configs to be picked up by new Cx mechanisms.
To be added:
For lifecycle-manager and modulectl kind value of
kcp
should be used, for runtime-watcher and template-operator kind iskyma
.Reasons
Security compliance
Acceptance Criteria
Feature Testing
No response
Testing approach
No response
Attachments
No response
The text was updated successfully, but these errors were encountered: