Fix incorrect header name for api key in alerting client. #633
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Kibana doesn't support api key prior to that version.
tobio
previously approved these changes
May 15, 2024
tobio
approved these changes
May 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The wrong header name is brought by regenerating Kibana alerting OpenAPI specs from
https://raw.githubusercontent.com/elastic/kibana/8.7/x-pack/plugins/alerting/docs/openapi/bundled.json
I've tried to use 8.12 but got a few compilation errors so decided to implement an approach similar to the one we use for SLO and data view clients.
Rel: #632