Add support to parse oscal document #17
Conversation
|
@abunashir we should update the oscal gem and republish the latest version for the coradoc-oscal functionality to work |
oscal.yml
Outdated
| - !ruby/object:Oscal::Control | ||
| id: cls_5.1 | ||
| props: | ||
| - !ruby/object:Oscal::Property |
There was a problem hiding this comment.
@abunashir is it possible to remove the Ruby class designator here? I thought we just need to call Oscal::Catalog.to_yaml and the YAML file would not contain classes.
This is a "defined YAML structure" for OSCAL, we cannot change it by inserting Ruby-specific content.
There was a problem hiding this comment.
It is possible, but I assume we have to fix the to_yaml issue in Oscal and their Objects. For now, I just double transformed the doc and that should fix the issue for now. But, we definitely have to fix that soonish.
There was a problem hiding this comment.
Yes we will need to update the to_yaml methods in the OSCAL gem. The back is okay for now. Thanks.
This is the task:
There was a problem hiding this comment.
I can verify that the hack works. Thanks.
This commit adds base support to parse an OSCAl document, this also provides a simplified way to get the ascidoc parsed into a structured YAML document. To parse any oscal document we can use the following. ```ruby Coradoc::Oscal.parse_to_yaml(sample_oscal_adoc) ```
abunashir
changed the title
This commit adds base support to parse an OSCAl document, this also provides a simplified way to get the ascidoc parsed into a structured YAML document. To parse any oscal document we can use the following.