Actions
Bug #22378
closedGenerate policies for campaigns before it starts officially, delete them after it stops (1 hour delay each)
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
We want to distribute campaign policies before they need to be applied so that they are correcly deployed before it needs, and keep them applied after offcial end of the campaign so that the node could still send reports if they reboot after.
EDIT: This is to handle problems that may arise in step 2 and 4 of scheduling management detailed in https://issues.rudder.io/issues/22130
Actions