-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add new target-manifest flag for user to provide a manifest (file) of file/directory paths to validate #50
Comments
@jordanpadams @galenatjpl What is the different between "a set of files/directories to validate." and "a list of files/directories to validate"? Do you have a example file of manifest (file)? |
@danyu-pds I don't have one off-hand, but you can think of it as a file containing a list of files/directories separated by newlines, e.g.
|
OK. Will do. |
products to validate Added new option "--target-list-file" for the command line and "validate.targetListFile" for the config file. Modified index.xml.vm for the new option.
Added new option "--target-list-file" for the command line and Modified index.xml.vm for the new option. To test: Check the target files in the report (Parameters:Targets). |
products to validate Added new option "--target-list-file" for the command line and "validate.targetListFile" for the config file. Modified index.xml.vm for the new option.
…irectory paths (#103) * issue #50:Add capability for User to provide a manifest (file) of products to validate Added new option "--target-list-file" for the command line and "validate.targetListFile" for the config file. Modified index.xml.vm for the new option. * Update flag to target-manifest Updates also include integration tests and updated documentation. * Update config key to validate.targetManifest * Add test data
Current
--target
flag supports the ability to specify a set of files/directories to validate.Create a new flag that allows for a
target-manifest
to be specified that contains a list of files/directories to validate.The text was updated successfully, but these errors were encountered: