My main concern is the first line: Warning: Unexpected input(s) 'options', valid inputs are ['entryPoint', 'args', 'full']
Another question (but unrelated to the --options issue): does this matter? -> ERROR: NotifyClamd: Can't find or parse configuration file /etc/clamav/clamd.conf
Additional context
Just trying to scan binaries in a directory, along the lines of #20.
(I also tried with djdefi/gitavscan@main, but no change.)
Describe the bug
I want to scan one sub-directory of my workspace and therefore use the new option to pass options to clamav.
To Reproduce
I'm using this syntax in my GitHub Action yml file:
The releasefiles directory contains binaries to be scanned.
Expected behavior
I expect this configuration to not raise errors or warnings.
Note that I am not sure if the directory is scanned or not. But the log message suggests that the "options" parameter is not recognized.
Screenshots
This is the log output:
My main concern is the first line:
Warning: Unexpected input(s) 'options', valid inputs are ['entryPoint', 'args', 'full']
Another question (but unrelated to the --options issue): does this matter? ->
ERROR: NotifyClamd: Can't find or parse configuration file /etc/clamav/clamd.conf
Additional context
Just trying to scan binaries in a directory, along the lines of #20.
(I also tried with djdefi/gitavscan@main, but no change.)