Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BuildDropPath and BuildDropPath - Parameter description #890

Closed
rmkanda opened this issue Jan 22, 2025 · 1 comment
Closed

BuildDropPath and BuildDropPath - Parameter description #890

rmkanda opened this issue Jan 22, 2025 · 1 comment
Assignees
Labels
accepted We are working on this and hope to release it into the product

Comments

@rmkanda
Copy link

rmkanda commented Jan 22, 2025

Hi Team,

Can we update the description of BuildDropPath and BuildComponentPath arguments, so that is clear for users?

Before:

BuildDropPath (-b)                        The root folder of the drop directory for which the SBOM file will be generated.
BuildComponentPath (-bc)                  The folder containing the build components and packages.

After:

BuildDropPath (-b)                             Specifies the root folder of the drop directory containing the final build artifacts (binaries and executables) for which the SBOM file will be generated. 
                                               This is the directory where the completed build output is stored.
BuildComponentPath (-bc)                       Specifies the folder containing the source code and components used to build the binary. 
                                               This is where the tool will look for the individual components and packages that are part of the build process.
@sfoslund sfoslund added needs triage Default status upon issue submission accepted We are working on this and hope to release it into the product and removed needs triage Default status upon issue submission labels Jan 23, 2025
@sfoslund sfoslund self-assigned this Jan 23, 2025
@rmkanda
Copy link
Author

rmkanda commented Jan 27, 2025

Thanks @sfoslund

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted We are working on this and hope to release it into the product
Projects
None yet
Development

No branches or pull requests

2 participants