Introduction
The document describes steps to run different reports configured using pipelines created by energizers team
The reports are generated by leveraging data stored by different soup automation utilities into three databases - productcatalogue, soupinventorydata and releasedependency
Following reports are available
Un-managed dependency report
You can use this report to find the dependencies that are not managed through artifact feeds or soup inventory repo (filtered by product or by repo ). This means that the artifact is not managed as per the P&P here. For such artifacts soupinventorydata database will not be populated with information about the soup item and therefore the corresponding soup reports will not be complete
To generate the report execute steps defined here
Out of date report
You can use this report to find the dependencies that are out of date (filtered by product or by repo ). This is based on semantic versioning. Three types of report are available - report of artifacts with major version update available, artifacts with minor version update available and artifacts with patch version update available. Developers/architects can pull this reports and identify the artifacts with updates available that can avoid vulnerabilities or improve performance or that has bugs fixed (especially a major version update, which will be usually a breaking change)
To generate the report execute steps defined here
Where used report
You can use this report repo or product that uses an artifact. This report will be useful in the scenario like if there is a major issue found with an artifact, you can run this report using that artifact as parameter and easily identify the products/repos that are using the artifact
To generate the report execute steps defined here