arcsector

Happening again now

Can you submit your CLI command you used to generate this, and also use the verbose output flag on the command

Here's my reproduction using a public image `ackstorm/debian-postfix:latest`: ```> podman run aquasec/trivy image --trace --debug ackstorm/debian-postfix:latest 2023-08-18T21:56:03.246Z DEBUG Severities: ["UNKNOWN" "LOW" "MEDIUM" "HIGH" "CRITICAL"] 2023-08-18T21:56:03.248Z DEBUG Ignore statuses {"statuses": null}...

@dtwersky I think this can be closed with the merging of https://github.com/splunk/ansible-role-for-splunk/commit/e6d5ab3286748a7c922b0398b025761dd4c4d13a

Any update on this issue?

Would this be something that would need to be done for both UFs and Full installs, or just Full? Last I heard from Splunk support, they don't have OOTB support...

Made some changes to put the unfound items at the top of the file. Note that even if you set the file correctly, and the REST API shows you have...

1. Yes, this is the desired functionality, change the level now, and then do it persistently so a restart isn't necessary. I can remove the restart handle to reflect this....

Possible other features to include: - KVStore Restore from backup - KVStore Clean - KVStore Resync - Oplog change in SHC

Fixed all the auth issues (sorry it slipped my mind) in https://github.com/splunk/ansible-role-for-splunk/pull/177/commits/ce2c80a4bbd06fedb016c01c403d2b927a4abdf6