Disabled automated pipelines

[deepsidhu85]

Summary

Currently within IRIDA Next, a previously automated and executable pipeline can be updated to not be executable or automated through the config. If one of these pipelines are set-up for a project, there is no way for the users to be notified that the pipeline is no longer executable, automated, or both

Acceptance Criteria

• New db column to store if the automated workflow execution is enabled/disabled
• config/initializers/pipelines.rb initializer updated to contain an after_initialize hook which will update the automated workflow executions table to set the enabled/disabled state of the automated pipeline. See the link below for more information on initializers
• UI: Automated workflow executions table within projects updated to include this new state column

Links

https://guides.rubyonrails.org/configuring.html#initialization-events