-
Notifications
You must be signed in to change notification settings - Fork 20
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
POA&M conversion from XML to JSON creates an assessment-plan #96
Comments
Thanks for this report, I and the team will look at this when we have time and bandwidth. I appreciate it, Gary. |
@GaryGapinski thanks for this. I had a few developers resurface this bug in a different context and it appears it is something I will have to troubleshoot and look for a fix. /cc @volpet2014 |
I talked with Dave and found one example of the issue: Next steps:
|
I added some tests and merged into |
This appears to be corrected.
|
I will close this for now but will need to prepare a release later in the week. Thanks for your quick feedback, @GaryGapinski. |
Refactored CLI handling based on a number of metaschema-java improvments, to include better exit code handling, and improved command re-usability across projects. Added support for the "metaschema validate-content" command. Included test code for usnistgov#96, and testing YAML nulls. Some code formatting cleanup.
* Integrated new version handling in CLI from metaschema-java. Refactored CLI handling based on a number of metaschema-java improvments, to include better exit code handling, and improved command re-usability across projects. Added support for the "metaschema validate-content" command. Included test code for #96, and testing YAML nulls. Some code formatting cleanup. * Improve the GHA build. Similar to liboscal-java.
* Integrated new version handling in CLI from metaschema-java. Refactored CLI handling based on a number of metaschema-java improvments, to include better exit code handling, and improved command re-usability across projects. Added support for the "metaschema validate-content" command. Included test code for #96, and testing YAML nulls. Some code formatting cleanup. * Improve the GHA build. Similar to liboscal-java.
Describe the bug
Attempted a conversion of an OSCAL
plan-of-action-and-milestones
document from XML to JSON. Output document wasassessment-plan
.I was interested in the problem discussed in usnistgov/OSCAL#961.
Who is the bug affecting?
oscal-cli
users.What is affected by this bug?
OSCAL POA&M XML to JSON conversion.
When does this occur?
Using
oscal-cli version 0.3.0 built on 2023-01-26 17:30 on commit 627d772
.How do we replicate the issue?
Something analogous to the following.
The output document is
Contrast that output with
Expected behavior (i.e. solution)
The converted document should be an OSCAL
plan-of-action-and-milestones
document in JSON format.The text was updated successfully, but these errors were encountered: