Actions
User story #3015
openAllow to schedule activation or disactivation of rules
Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
We want to be able to enable or disable a Rule at a given Time/Date.
The schedule is configure directly in the rule's configuration screen.
Note that enabling or disabling a rule thanks to that mean actually trigger a Rule modification, and so that modification is submitted to validation retention rules (rudder.autoDeployOnModification=false)
So, we have to take special advertisement when validating deployment is enable:
- replace scheduled action configuration with the message "Scheduling Rules to be enabled/disabled at a given date and time is not compatible with manual promise deployments, which you have enabled. To make use of this feature, set the rudder.autoDeployOnModification property to "true" in Rudder's configuration (/opt/rudder/etc/rudder-web.properties)."
- add to "rudder.autoDeployOnModification"'s property description "WARNING: This feature is required to be able to schedule Rules to enabled/disabled at a given date and time. If set to "false", automatic enabling/disabling of Rules will not function."
- when the application start, if "rudder.autoDeployOnModification=false" then we have to check if there is some Rules with action scheduled, we log a warning in "rudder-core"'s log (and "webapp") saying: "ERROR: rudder.autoDeployOnModification is disabled, but the following Rules are set to be scheduled to be enabled/disabled at a given date and time. This schedule can NOT be respected unless rudder.autoDeployOnModification is enabled in configuration: UUID1, UUID2, ...".
- scheduled action are not erased when Rudder restart, even if rudder.autoDeployOnModification=false.
That bug is a meta-ticket, implementation, integration and documentation will be open in children tickets.
Updated by François ARMAND about 12 years ago
- Status changed from New to 8
- Target version set to 24
Updated by Nicolas CHARLES almost 12 years ago
- Target version changed from 24 to 2.6.0~beta1
It won't go it 2.5, retargetting to 2.6
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.6.0~beta1 to 2.6.0~rc1
Updated by Matthieu CERDA over 11 years ago
- Target version changed from 2.6.0~rc1 to 2.6.0
Updated by Jonathan CLARKE over 11 years ago
- Target version changed from 2.6.0 to 2.6.1
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.6.1 to 2.6.2
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.6.2 to 2.6.3
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.6.3 to 2.6.4
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.6.4 to Ideas (not version specific)
Actions