-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes data type inconsitency in Apply alert tags API #4581
Conversation
A documentation preview will be available soon.
Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change looks good - thanks @natasha-moore-elastic!
@dplumlee just to double-check, is the kibana.alert.workflow_tags
alert field description correct here as well?
@nastasha-solomon Yes, that's the field itself so it should just be a keyword array, we only use the object with |
(cherry picked from commit 418ddf5)
(cherry picked from commit 418ddf5)
(cherry picked from commit 418ddf5)
(cherry picked from commit 418ddf5)
(cherry picked from commit 418ddf5) Co-authored-by: natasha-moore-elastic <[email protected]>
(cherry picked from commit 418ddf5) Co-authored-by: natasha-moore-elastic <[email protected]>
(cherry picked from commit 418ddf5) Co-authored-by: natasha-moore-elastic <[email protected]>
(cherry picked from commit 418ddf5) Co-authored-by: natasha-moore-elastic <[email protected]>
Fixes #4567 by updating the
tags
parameter's data type in the description to object.Preview: Signals endpoint