feat!: add options pattern to OSCAL catalog generation #206
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR updates the OSCAL generation logic post-move. The Layer 1 and Layer 2 approaches were somewhat divergent. Now that they are in the same package, we can reuse the functional options approach from Layer 1. Adds OSCAL-CLI validation CI to ensure there are no validation failures.
Schema Changes
Schema Changes Made
schemas/layer-1.cue) changesschemas/layer-2.cue) changesschemas/layer-3.cue) changesschemas/layer-4.cue) changesSchema Change Details
Testing
Related Issues
Closes #142
Reviewer Hints
The code is primarily reorganized, but
CatalogFromCatalogwas also updated and uses theGenerateOptionsnow.