Put command into queue that activates pipeline again at a certain time in the future
The problem with this is, that you cannot easily prolong the silence period of a pipeline (Basically, you'd have to remove the initial reactivation command from the command queue which is a bit complicated). So I suggest the following:
allowed values for a pipeline's status: 'active', 'inactive' (no more silent status)
Wether or not a pipeline is silent is determined via the silent_until field in its DB doc.
if silent_until > current time or == -1 (silent forever) the pipeline is silent else it's not
This should already include all the changes, but requires testing.
This change also needs a small tweak in doberview.
Currently, silencing works as follows:
silentThe problem with this is, that you cannot easily prolong the silence period of a pipeline (Basically, you'd have to remove the initial reactivation command from the command queue which is a bit complicated). So I suggest the following:
silent_untilfield in its DB doc.silent_until > current time or == -1 (silent forever)the pipeline is silent else it's notThis should already include all the changes, but requires testing. This change also needs a small tweak in doberview.