Replace jq in ci-templates
Problem to solve
The usage of jq
in the ci-templates
files has become increasingly complex and difficult to maintain without introducing bugs or other unintended side effects.
Intended users
Further details
As discussed here, it's time that we revisit our usage of jq
and investigate alternate approaches that are easier to maintain and can be tested to confirm correct operation.
Proposal
Create a new tool to implement the jq
logic found in the following files:
- analyzer.yml
- qa-code_quality.yml
- qa-container_scanning.yml
- qa-dast.yml
- qa-dependency_scanning.yml
- qa-license_management.yml
- qa-license_scanning.yml
- qa-sast.yml
Documentation
Documentation for the tool should be provided in the README
file for the tool
Availability & Testing
Add unit tests to ensure that the comparison logic is properly implemented.
Tests to be implemented in another issue: Add tests for compare_reports script in ci-templates project
What is the type of buyer?
groupcomposition analysis groupstatic analysis groupdynamic analysis
Links / references
Edited by Adam Cohen