-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
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
chore: sc-sast scan start --sargs
scaRuntimeArguments support added
#487
Conversation
tests are disabled for now since config has to be switched to a new tenant for mobile scans to work
added oss only package, apk for mast scan
FoD test updates
We'd need to double-check exact SC SAST behavior with regards to interaction between |
The documentation lists the supported options : And yes, for custom rules and filter files, they have to be available on the sensors. |
ScanCentral expects the package.zip file inside another zip file (which is created by fcli on the fly); I guess these extra filer/template/rule files go into the outer zip file, not the zip-file created by |
indeed. What about adding an we could also do it automatically like |
77df0de
to
78505cb
Compare
Superseded by #627, which adds support for including local files in scan payload. |
#198
#449
The added fcli
--sargs --sca-args
option allows specify scan args along with other arguments such as -filter (see accepted arguments)As of --targs, with current fcli support, there is no need for it.
Currently, we can only start a sast scan using package or mbs. These two options do not support/requires translation arguments (targs are passed to the
scancentral package
cmd, and mbs are already translated)