-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
2.4
-
False
-
-
False
Currently, notifications are linked to either Job Templates or Workflow templates. But it's entirely possible to kick off a scheduled run of a Job template Twice with different limits or customized runtime arguments. It'd be really awesome if we could have notifications available to us as part of the schedule module.
Use case example:
I have a Job Template that runs a Token Rotation playbook. I have two schedules for this playbook - one for "prod" group and one for "nonprod" group. I'd like to be able to have notifications fire for the prod one but not the nonprod one.
My current solution would be to create two separate job templates or workflow templates linked to the same playbook just with different hardcoded values, but why create 4 objects (2 schedules, 2 job templates) when it should be possible to do this via schedule?
Value or Impact:
Trying to keep the amount of superfluous job templates low, as job template bloat is a real problem we experience.