-
Notifications
You must be signed in to change notification settings - Fork 96
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
Revise inter-boundary-component-has-direction constraint (#930) #988
Revise inter-boundary-component-has-direction constraint (#930) #988
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like this PR not get merged until we confirm this implements the updated in a comment but not modified in the issue criteria per #930 (comment). I just want confirmation that this is "the place" where that goes because thus far the new requirements were discussed separate of which issue, this seems like one possible place. If I get corrected by someone on the team, I will dismiss and approve.
I only delinked #930 so it does not automatically close the issue because there are potentially multiple requirements for that set of constraints, I do not want to automatically close. I am about to re-review. |
Committer Notes
fedramp-external-constraints.xml
, modify thetarget
Metapath expression (theinter-boundary-component
variable).ssp-inter-boundary-component-has-direction-INVALID.xml
to reflect Metapath changes.Related issue: #930
All Submissions:
By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.