Add operations for container scan to status.json #960
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add operations for Container Scan to the "operations" section in the status.json. Addresses only one part of IDETECT-4086 where container scan operations were not being reported to status.json.
The main thing to note in this PR is that to report an operation in status.json, the container scan operations have been wrapped using the below 2 wrapper methods:
auditLog.namedInternal(String operationName, OperationWrapper.OperationFunction supplier)
The
namedInternal
wrapper will report an operation to status.json only if there was a failure during the supplier's execution.auditLog.namedPublic(String operationName, OperationWrapper.OperationFunction supplier)
The
namedPublic
wrapper will always report an operation to status.json - irrespective of execution status.JIRA
IDETECT-4086