-
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 capability for user to input JSON file with additional context products #28
Comments
@jordanpadams |
@danyu-pds both not-registered_context_products file and registered_context_products file . in addition, when the not-registered_context_products file is specified, we should throw a warning that this should be used for archive development only, and all context products need to be registered for a valid released archive bundle. |
OK. |
context products Added option --no-registe-prod-context <dir/file.json> to give the not-registered_context_products JSON file. Created Product_Context map with REGISTERED_PRODUCTs and NON_REGISTERED_PRODUCTs if it is available. Added a problem type NON_REGISTERED_PRODUCT for warning message.
Added option --no-registe-prod-context <dir/file.json> to give the Created Product_Context map with REGISTERED_PRODUCTs and Added a problem type NON_REGISTERED_PRODUCT for warning message. To test this: For example: In the output of report will see: Product Level Validation Results PASS: gov.nasa.pds.validate.ValidateLauncher Summary: 0 error(s) Message Types: End of Report |
… context products (#60) * issue #28: Add capability for user to input JSON file with additional context products Added option --no-registe-prod-context <dir/file.json> to give the not-registered_context_products JSON file. Created Product_Context map with REGISTERED_PRODUCTs and NON_REGISTERED_PRODUCTs if it is available. Added a problem type NON_REGISTERED_PRODUCT for warning message. * Fixed a typo * Updates to error handling and CLI info * Added error handling for bad JSON file * Modified CLI info to be more user-friendly
Issue #28: Integration tests for new feature checkout
For development purposes, a data producer may have context products that are not registered that are in their data products being validated. Right now, documentation notes user should update JSON config file with additional products.
This new feature should allow for a JSON file to be included via command-line instead of requiring an update to the existing config file.
The text was updated successfully, but these errors were encountered: