-
Notifications
You must be signed in to change notification settings - Fork 356
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: async DELETE experiment [DET-5804] #2741
Conversation
✔️ Deploy Preview for determined-ui ready! 🔨 Explore the source changes: d9df59d 🔍 Inspect the deploy log: https://app.netlify.com/sites/determined-ui/deploys/60f8345c206771000703945c 😎 Browse the preview: https://deploy-preview-2741--determined-ui.netlify.app/ |
master/static/migrations/20210716133048_add-deleting-states.down.sql
Outdated
Show resolved
Hide resolved
master/static/migrations/20210716133048_add-deleting-states.up.sql
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
overall it lgtm I posted a question about the experiment while deletion is happening.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢
Description
This change adds the
DELETING
andDELETE_FAILED
states to experiments and changesDELETE /api/v1/experiments/<id>
to work asynchronously. Now upon aDELETE
, after all validation happens, the experiment is moved to theDELETING
state and the deletion takes place asynchronously. If it fails, the experiment is moved to theDELETE_FAILED
state. Also on master restart, allDELETING
experiments are moved toDELETE_FAILED
.DELETE_FAILED
can be retried manually by the user, but it not retried automatically since it would likely fail if it failed recently.Test Plan
Commentary (optional)
Checklist
docs/release-notes/
.See Release Note for details.