We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We will remove the obsolete has-separation-of-duties-matrix as we make room for #809 and not confuse community evaluating the rules out of develop
develop
This is required core OSCAL syntax.
There are no relevant allowed values.
<!-- not applicable -->
No response
oscal-cli metaschema metapath eval -e "expression"
This removal will make way for alternative approach upcoming in #809.
(/cc @Telos-sa for awareness as it came up recently during an office hours, you may disregard that constraint violation fro the time being.)
The text was updated successfully, but these errors were encountered:
has-separation-of-duties-matrix
Gabeblis
Successfully merging a pull request may close this issue.
Constraint Task
Intended Outcome
We will remove the obsolete has-separation-of-duties-matrix as we make room for #809 and not confuse community evaluating the rules out of
develop
Syntax Type
This is required core OSCAL syntax.
Allowed Values
There are no relevant allowed values.
Metapath(s) to Content
<!-- not applicable -->
Purpose of the OSCAL Content
No response
Dependencies
No response
Acceptance Criteria
oscal-cli metaschema metapath eval -e "expression"
.Other information
This removal will make way for alternative approach upcoming in #809.
(/cc @Telos-sa for awareness as it came up recently during an office hours, you may disregard that constraint violation fro the time being.)
The text was updated successfully, but these errors were encountered: