You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
This issue has been marked as stale because it has not been commented on in two months.
Please reply in order to keep the issue open. Otherwise, it will close in 14 days.
Thank you for contributing!
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: