-
Notifications
You must be signed in to change notification settings - Fork 91
Allow "results" to be uploaded after task run #1086
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
Comments
This issue has been marked as stale because it has not been commented on in two months. |
Came to suggest something like this as well. It would be extremely helpful to record the result of a |
This issue has been marked as stale because it has not been commented on in two months. |
This issue has been marked as stale because it has not been commented on in two months. |
This issue should probably be reopened. It's tracking a clearly desirable feature. |
Our application has a few maintenance tasks which iterate over a collection and then upload a CSV with the results of the task. This is implemented using the
after_start
/after_complete
/after_error
callbacks and by flushing to a CSV after each iteration.What would be neat is if this feature was baked into the gem by default, and the results uploaded was all handled by ActiveStorage and stored on the run model. This would mean that viewing past runs would be able to surface a deep-link to this "results" file.
Is this something that PR's would be accepted for?
The text was updated successfully, but these errors were encountered: