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

Filtering for sandbox #4216

Merged
merged 4 commits into from
Jan 24, 2022
Merged

Filtering for sandbox #4216

merged 4 commits into from
Jan 24, 2022

Conversation

nmanovic
Copy link
Contributor

Motivation and context

There 3 modes for IAM:

  1. org=slug only corresponding objects for the organization are visible
  2. org= only objects outside an organization are visible
  3. None all own or assigned objects are visible (admin can see all objects)

How has this been tested?

Manually

Checklist

  • I submit my changes into the develop branch
    - [ ] I have added a description of my changes into CHANGELOG file
    - [ ] I have updated the documentation accordingly
    - [ ] I have added tests to cover my changes
    - [ ] I have linked related issues (read github docs)
    - [ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
    cvat-core, cvat-data and cvat-ui)

License

  • I submit my code changes under the same MIT License that covers the project.
    Feel free to contact the maintainers if that's a concern.
  • I have updated the license header for each file (see an example below)
# Copyright (C) 2022 Intel Corporation
#
# SPDX-License-Identifier: MIT

Nikita Manovich added 2 commits January 20, 2022 16:44
Now we have 3 types of visibility (aka org_filter)
1. org=slug - see objects only for the organization
2. org=     - see objects only for sandbox (organzation is None)
3. None     - see all objects which you can access
@nmanovic nmanovic requested review from sizov-kirill and removed request for bsekachev January 20, 2022 20:36
@nmanovic
Copy link
Contributor Author

@kirill-sizov , could you please look at the PR? It will be interesting to run your new tests as well.

@sizov-kirill
Copy link
Contributor

@kirill-sizov , could you please look at the PR? It will be interesting to run your new tests as well.

Yes, sure.

Copy link
Contributor

@sizov-kirill sizov-kirill left a comment

Choose a reason for hiding this comment

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

All my tests that I have have been passed. Code changes LGTM

@nmanovic nmanovic merged commit 5ccc596 into develop Jan 24, 2022
@nmanovic nmanovic deleted the nm/org_filtering branch January 24, 2022 12:22
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.

3 participants