Skip to content
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

fix(policy): DSP-54 make MatchSubjectMappings operator agnostic #1658

Draft
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

suchak1
Copy link
Contributor

@suchak1 suchak1 commented Oct 16, 2024

resolves: #1499

@suchak1 suchak1 changed the title fix(policy): make MatchSubjectMappings operator agnostic fix(policy): DSP-54 make MatchSubjectMappings operator agnostic Oct 16, 2024
where += "((" + hasField + " AND " + hasValue + " AND " + hasInOperator + ")" +
" OR " +
"(" + hasField + " AND NOT " + hasValue + " AND " + hasNotInOperator + "))"
// Parses the json and matches the row if the selector exists:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't touch this RPC to avoid merge conflicts, but perhaps you could remove this check and move it to the proto validation as part of this effort? https://github.com/opentdf/platform/pull/1658/files#diff-79178ab55805aac9e744330a45936ecde9e39baef7e8838764209f44b6a3f862R535 Similar to the work just done in GetAttributesByValueFQNs: #1657

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also think we can ignore a check for values now that this route only drives based off selectors (explicitly not values after your current work here): https://github.com/opentdf/platform/pull/1658/files#diff-79178ab55805aac9e744330a45936ecde9e39baef7e8838764209f44b6a3f862R542

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Policy: MatchSubjectMappings should be operator agnostic
2 participants