Added UI run action buttons #580
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Added restore api call in RunViewSet. - Added hooks file for django-q async_task hooks. - Added restore test. - Fixed deprecation warning in test compare_runs. - Added hooks.py to mkdocs.
- Makes calling the command from the website much easier. - Removed hooks. - Reverted the restorepiperun script.
- Allowed for users to delete their runs. - Allowed for users to generate arrow files for their run. - Added new pipeline status of `DEL`, `Deleting`.
- Updated documentation. - Fixed restore relations (#579).
ajstewart
added
documentation
[skip ci]
marxide
approved these changes
Oct 8, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds action buttons to the run detail page to allow users to perform actions through the UI that had only been available to admins via the CLI.
Specifically users can now:
Which all uses the existing django-q processing (and using the Django
call_commandwhich makes things much more straight forward).I have tested as much as possible but they all use the same user check as the process run command so it should all be good. Probably best to test it in a dev env through with lots of users.
It also includes:
For the deletion from the UI I decided to make it so that the remove all option is used - i.e. the whole directory is removed. I thought that from the UI it made sense to remove everything. Otherwise that name of job will be forever blocked off without someone going in and removing the run directory.
Built on top of #576, that should be looked at first.
Fixes #579.
Screenshots:
