-
Notifications
You must be signed in to change notification settings - Fork 444
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
Update input types and vars to support runtime config #3968
Conversation
🌐 Coverage report
|
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.
let's
conditions:
kibana.version: "^8.5.0"
So this won't break the current 8.4 release
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.
Merge with the proper changes in Kibana & cloudbeat
type: yaml | ||
title: Rules Activation Yaml | ||
title: Rules Activation |
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.
consider changing the title to Configuration used for evaluation
or something similar that better describes this field
Co-authored-by: eyalkraft <63912106+eyalkraft@users.noreply.github.com>
- version: "0.0.27" | ||
changes: | ||
- description: Update input types and var name to support runtime config | ||
type: enhancement | ||
link: https://github.com/elastic/integrations/pull/3968 | ||
- version: "0.0.26" | ||
changes: | ||
- description: Version bump | ||
type: enhancement | ||
link: https://github.com/elastic/integrations/pull/3997 | ||
- description: Updates to KSPM Integration README | ||
type: enhancement | ||
link: https://github.com/elastic/integrations/pull/3964 |
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.
Since 0.0.26 wasn't promoted yet we can unify it under it, no?
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.
This pr introduces breaking changes so we want to promote version 0.26 to SNAPSHOT and only then merge this commit.
The Kibana version condition changed to ^8.5.0.
What does this PR do?
dataYaml
var toruntimeCfg
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots