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

Fabric filtered write for access control #14437

Closed
mlepage-google opened this issue Jan 27, 2022 · 1 comment
Closed

Fabric filtered write for access control #14437

mlepage-google opened this issue Jan 27, 2022 · 1 comment
Assignees
Labels
acl Access Control feature V1.0

Comments

@mlepage-google
Copy link
Contributor

Fabric filtered read is done, fabric filtered write is still in progress, and depends on IM support (PR #13756).

Also the cluster needs to use the module's fabric filtered indexing mode; that PR includes that small code change to do so.

Still will need end to end testing.

@mlepage-google mlepage-google self-assigned this Jan 27, 2022
@mlepage-google mlepage-google added acl Access Control feature V1.0 labels Jan 27, 2022
@andy31415 andy31415 added v1_triage_split_5 V1.0 acl Access Control feature and removed V1.0 acl Access Control feature labels Jan 30, 2022
@mlepage-google
Copy link
Contributor Author

Now that #13756 is merged, and with one-line fix #14670, I have tested locally that fabric filtered write works properly, by writing from two different fabrics using all-clusters-app on Linux. Automated tests for the cluster are covered in #10253.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acl Access Control feature V1.0
Projects
None yet
Development

No branches or pull requests

3 participants