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.

Sign up for GitHub

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

Jump to bottom

[Feature]: mark in-use data-sets as read-only #338

Open
kitsudaiki opened this issue Jun 9, 2024 · 0 comments
Open

[Feature]: mark in-use data-sets as read-only #338

kitsudaiki opened this issue Jun 9, 2024 · 0 comments
Labels
Breaking: DB-Schema Changes in the schemas of database tables Env: Documentation requires an update of the documentation Env: Test updates in test-code (functional-tests and so on) L: ★★☆ Expect mid difficulty New feature / Improvement new features and improvements of existing features Topic: Security security-bugs Topic: Usability changes to improve the usability of the program
Milestone
0.6.0

Comments

@kitsudaiki
Copy link
Owner

Feature

Description

Data-sets, which are used by a task, should be marked as read-only within the database to prevent them from deletion.

Acceptance Criteria

  • data-set tables have a new column to track the avaiability
  • data-sets are marked as read-only, when a task is created, which will use the data-set
  • data-sets can not be deleted as long as they are marked as read-only

Additional Information

Blocked by

How to test

  • create a data-set
  • use data-set in a task
  • try to delete the data-set as fast as possible, while the task is still running
@kitsudaiki kitsudaiki added Env: Documentation requires an update of the documentation New feature / Improvement new features and improvements of existing features Topic: Security security-bugs Env: Test updates in test-code (functional-tests and so on) Topic: Usability changes to improve the usability of the program Breaking: DB-Schema Changes in the schemas of database tables L: ★★☆ Expect mid difficulty labels Jun 9, 2024
@kitsudaiki kitsudaiki added this to the 0.5.0 milestone Jun 9, 2024
@kitsudaiki kitsudaiki self-assigned this Jun 9, 2024
@kitsudaiki kitsudaiki modified the milestones: 0.5.0, 0.6.0 Jul 14, 2024
@kitsudaiki kitsudaiki removed their assignment Aug 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Breaking: DB-Schema Changes in the schemas of database tables Env: Documentation requires an update of the documentation Env: Test updates in test-code (functional-tests and so on) L: ★★☆ Expect mid difficulty New feature / Improvement new features and improvements of existing features Topic: Security security-bugs Topic: Usability changes to improve the usability of the program
Projects
Hanami
Status: No status
Milestone
0.6.0
Development

No branches or pull requests
1 participant
@kitsudaiki