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
feat(Datasets): restrict dataset deletion only to creators and super-users #1713
Conversation
Codecov ReportBase: 95.66% // Head: 95.64% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #1713 +/- ##
==========================================
- Coverage 95.66% 95.64% -0.03%
==========================================
Files 147 147
Lines 6720 6722 +2
==========================================
Hits 6429 6429
- Misses 291 293 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Co-authored-by: Daniel Vila Suero <daniel@recogn.ai>
…users (#1713) * feat(Datasets): restrict dataset deletion only to creators and super-users * tests: add tests for datasets deletion check * chore: improve deletion error message Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> * Format long strings Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> (cherry picked from commit c5ab270)
…users (#1713) * feat(Datasets): restrict dataset deletion only to creators and super-users * tests: add tests for datasets deletion check * chore: improve deletion error message Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> * Format long strings Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> (cherry picked from commit c5ab270)
…users (#1713) * feat(Datasets): restrict dataset deletion only to creators and super-users * tests: add tests for datasets deletion check * chore: improve deletion error message Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> * Format long strings Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> (cherry picked from commit c5ab270)
…users (#1713) * feat(Datasets): restrict dataset deletion only to creators and super-users * tests: add tests for datasets deletion check * chore: improve deletion error message Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> * Format long strings Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> (cherry picked from commit c5ab270)
…users (#1713) * feat(Datasets): restrict dataset deletion only to creators and super-users * tests: add tests for datasets deletion check * chore: improve deletion error message Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> * Format long strings Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> (cherry picked from commit c5ab270)
…users (#1713) * feat(Datasets): restrict dataset deletion only to creators and super-users * tests: add tests for datasets deletion check * chore: improve deletion error message Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> * Format long strings Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> (cherry picked from commit c5ab270) fix: handle separately 401 and 403 api errors in UI (#1740) Since the changes included in #1713, users without permission trying to delete datasets from UI will hit into a re-login operation. This PR handles separate authentication errors (401) and forbidden errors (403). We should find a better way to handle error codes and info in general.
…users (#1713) * feat(Datasets): restrict dataset deletion only to creators and super-users * tests: add tests for datasets deletion check * chore: improve deletion error message Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> * Format long strings Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> (cherry picked from commit c5ab270) fix: handle separately 401 and 403 api errors in UI (#1740) Since the changes included in #1713, users without permission trying to delete datasets from UI will hit into a re-login operation. This PR handles separate authentication errors (401) and forbidden errors (403). We should find a better way to handle error codes and info in general.
…users (#1713) * feat(Datasets): restrict dataset deletion only to creators and super-users * tests: add tests for datasets deletion check * chore: improve deletion error message Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> * Format long strings Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> (cherry picked from commit c5ab270) fix: handle separately 401 and 403 api errors in UI (#1740) Since the changes included in #1713, users without permission trying to delete datasets from UI will hit into a re-login operation. This PR handles separate authentication errors (401) and forbidden errors (403). We should find a better way to handle error codes and info in general.
…users (#1713) * feat(Datasets): restrict dataset deletion only to creators and super-users * tests: add tests for datasets deletion check * chore: improve deletion error message Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> * Format long strings Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> (cherry picked from commit c5ab270) fix: handle separately 401 and 403 api errors in UI (#1740) Since the changes included in #1713, users without permission trying to delete datasets from UI will hit into a re-login operation. This PR handles separate authentication errors (401) and forbidden errors (403). We should find a better way to handle error codes and info in general.
…users (#1713) * feat(Datasets): restrict dataset deletion only to creators and super-users * tests: add tests for datasets deletion check * chore: improve deletion error message Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> * Format long strings Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> (cherry picked from commit c5ab270) fix: handle separately 401 and 403 api errors in UI (#1740) Since the changes included in #1713, users without permission trying to delete datasets from UI will hit into a re-login operation. This PR handles separate authentication errors (401) and forbidden errors (403). We should find a better way to handle error codes and info in general.
This PR includes restrictions on dataset deletion. Only datasets the creator or super-users (with full workspaces access) can delete datasets
@dvsrepo just review the error message, pls