-
Notifications
You must be signed in to change notification settings - Fork 86
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
No 'value' in an 'hashes' object causes a runtime error #787
Comments
Thank you, this is a very useful bug report. We will track this down soon. More updates to follow. |
@Telos-sa, can you please provide the following specifically:
Thanks in advance for your continued reports, we appreciate it. |
oscal-cli --version
@aj-stein-gsa What argument did you want to see output of with --disable-schema-validation? The --version output? or the stack trace output? |
Can you please re-run the command that led to this stack track with the correct file like so And to make sure I am on the same page, can you please update the full command showing that failed validation command, with or without |
here it is with the command
|
This is a ...
improvement - something could be better
This relates to ...
User Story
When validating an OSCAL SSP using the enhanced oscal-cli (v2.2.0), if there is no 'value' element provided in an 'hashes' object then a runtime error occurs:
Example rlinks>hashes structure causing the runtime error:
Runtime error with stack trace:
This is only an issue with the enhanced oscal-cli (I used v2.2.0). This doesn't occur with the base oscal-cli from NIST (v1.0.3). Here is the error message output when using the base oscal-cli (v1.0.3):
Goals
Modify enhanced oscal-cli validation to yield an error message for missing hashes>value rather than causing a runtime error.
Dependencies
No response
Acceptance Criteria
Other information
No response
The text was updated successfully, but these errors were encountered: