Issue with how playbook priority works across multiple environments
Andrew Cook Member
Has anyone else had issue with how playbook priority works across multiple environments? For example, if I have two playbooks at the same priority and one is assigned to a specific environment and the other is assigned to "all environments" then I would expect the more specific playbook would run. How else can I create customer-specific playbooks without them getting clobbered by the general ones?
On our custom trigger for an all environment playbook, we add in [alert.environment] != <environment>, then the client specific one is used