-
Notifications
You must be signed in to change notification settings - Fork 572
Enable package compatibility checks with older Elastic stacks #740
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
Changes from all commits
948cde2
e4c2fff
74d6c14
4d39032
dec50ac
af7f455
bc7167f
0020bb9
0bc4a9e
ae739c4
44c40d3
c45ee22
074b26e
681fcf1
f813d12
df5654e
ed26c02
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,7 @@ | ||
| format_version: 1.0.0 | ||
| name: microsoft | ||
| title: Microsoft | ||
| version: 0.4.1 | ||
| version: 0.4.2 | ||
| description: Microsoft Integration | ||
| categories: | ||
| - "network" | ||
|
|
@@ -11,7 +11,7 @@ release: experimental | |
| license: basic | ||
| type: integration | ||
| conditions: | ||
| kibana.version: '^7.9.0' | ||
| kibana.version: '^7.11.0' | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I didn't understand why we need these
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's because of the fact that these packages are not compatible with older Kibana stacks.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I see. Is there a reason these changes are part of this PR? In other words, do we need these changes anyway even without this PR? Did the compatibility checks introduced in this PR catch that these packages needed kibana version bumps?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Yes, exactly this. Otherwise the CI for this PR will be red. |
||
| policy_templates: | ||
| - name: microsoft | ||
| title: Microsoft | ||
|
|
||
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.
So it seems we are calling a package as compatible if we are able to install it. Is this sufficient or do we also want to run tests for the package against the previous stack versions?
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.
No, I prefer to stick to installation as testing will elongate test execution much (+20minutes).
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.
Understood. Does installing a package result in any testing? In other words, what are the reasons this step would fail in CI?
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.
e.g. installation can check if all Kibana objects can be installed (correct migrationVersion field).