Adding GENERATE_SBOM configurable flag instead of hardcoding #2674
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Change Overview
Software Bill of Materials aka SBOM is a list of licenses for 3rd party dependencies used, which is required to be displayed to customers while releasing the code. To generate this, a specific buildkit setup is required. However, we don't need to generate SBOM during development. The SBOM flag was hardcoded to true in Kanister.
Instead, in the PR, we are passing it as a configurable flag which is by default false unless set to true.
Pull request type
Please check the type of change your PR introduces:
Issues
None
Test Plan