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

[ocis] Space Trashbin expiration #5499

Closed
5 tasks done
exalate-issue-sync bot opened this issue Feb 1, 2023 · 0 comments · Fixed by #5500
Closed
5 tasks done

[ocis] Space Trashbin expiration #5499

exalate-issue-sync bot opened this issue Feb 1, 2023 · 0 comments · Fixed by #5500
Assignees
Labels

Comments

@exalate-issue-sync
Copy link

exalate-issue-sync bot commented Feb 1, 2023

Description

User Stories

  • As a sysadmin i want to auto clean the trashbin of the users to save storage space

Value

Better Storage usage

Acceptance Criteria

  • oCIS tracks the time a file resides in the trashbin
  • There is a CLI command that wipes expired trash items which we can trigger via kubernetes tasks
  • If a file is restored and then deleted again, the retention time period starts again
  • The time period for files in the trashbin can be configured differently on personal spaces and project spaces (default 30 days [~tbaader] please confirm), needs to be possible to deactivate completely
  • We have a github issue with technical debt label that tracks changing to service accounts, see Note below.

Notes

When service accounts are available we need to revisit this because currently we have to impersonate the admin, list all spaces, impersonate a manager or owner for each space and then expire the trash.

Definition of ready

[ ] everybody needs to understand the value written in the user story
[ ] acceptance criteria has to be defined
[ ] all dependencies of the user story need to be identified
[ ] feature should be seen from an end user perspective
[ ] user story has to be estimated
[ ] story points need to be less then 20

Definition of done

  • Functional requirements
    [ ] functionality described in the user story works
    [ ] acceptance criteria are fulfilled
  • Quality
    [ ] code review happened
    [ ] CI is green
    [ ] critical code received unit tests by the developer
    [ ] automated tests passed (if automated tests are not available, this test needs to be created and passed
  • Non-functional requirements
    [ ] no sonar cloud issues
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant