Problem: pipelines can't be decommissioned or disabled temporarily

[joel-simpson]

Enduro queues and pushes work to Archivematica pipelines as it is fed new collections.

This means as long as the upstream process (SIP creation) is feeding new collections to Enduro, the pipeline will constantly be busy.

However we need to be able to run maintenance on an Archivematica pipeline (to truncate database tables, or upgrade the software, etc). We can't do this while the pipeline is still processing transfers or SIPs.

So we need a way to stop an new work being sent to an Archivematica Pipeline.

Somehow, the maintenance operator will need to know that the Pipeline is no longer processing any transfers or SIPs. Possibly this can already be done with Enduro -- by filtering on the pipeline, you'd see all of the collections in progress. You could also filter on state -- when there are no more collections in the state 'in progress', it should be safe to run maintenance on Archivematica.

[scollazo]

This should be possible in an automated way, without the need of operator intervention

[sevein]

To be clear, Santi is not asking for a mechanism that is self-activating but that can be triggered programmatically, presumably via the API.