Open
Description
openedon Jun 1, 2021
When the action executor runs, action parameters are validated against the parameter schema and an error is thrown when there is an invalid parameter. However, when a rule is created with actions, those action parameters are not validated. This means a rule with actions could be created successfully, but when the rule is triggered and its actions run, the actions will throw an error.
To create this scenario, create a rule with a Pagerduty action through the API and set the timestamp
field to null
in the action parameters. The rule creation returns a 200 but the first time the action tries to run, you will see logs like these:
Task actions:.pagerduty "e47b5ae0-c30e-11eb-83e4-695f9fbb4810" failed: Error: error validating action params: [timestamp]: expected value of type [string] but got [null]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Assignees
Labels
Issues related to the Actions attached to Rules on the Alerting FrameworkIssues related to the Rules Management UXLabel for the ResponseOps team (formerly the Cases and Alerting teams)Small Estimated Level of EffortIssues related to Platform resilience in terms of scale, performance & backwards compatibility