-
Notifications
You must be signed in to change notification settings - Fork 60
Migrate Alerting Kibana pluign to the new Kibana Platform #209
Changes from all commits
5f28e97
6dd8dee
d65ef1a
6cb4717
12bd463
8fb49bd
6351a01
37ca8d7
755b46e
3fde6e2
a34d7fb
fd0a9b7
71db812
32e202f
9acf695
c33e819
361394a
2ab8bd4
0e81849
045e51f
b54f75f
148f177
f135af1
618b447
2012070
71b5731
d61d0e2
ee4b086
841b4b2
f3f5aaa
0f1b13b
05271e6
9c74a64
46b9c91
efca040
a58666b
e5956a9
ace80f5
fa65396
28d1288
9ca0480
9cb2029
0f55cbd
d54a032
80be167
6c063a1
952f07f
e4ecbd4
4cb2c97
7e72b0d
f0b42b9
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 |
---|---|---|
|
@@ -11,3 +11,4 @@ build | |
.kibana-plugin-helpers.dev.json | ||
coverage | ||
yarn-error.log | ||
target |
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
{ | ||
"id": "opendistroAlerting", | ||
"version": "1.11.0.2", | ||
"kibanaVersion": "kibana", | ||
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. Specify kibana version as "kibana" will auto resolve as 7.10? 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. Hi Yaliang, thanks a lot for reviewing my PR. In my mind, it will resolve as the version defined in 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 comes from "kbn-plugin-generator", in the template of the sample Kibana plugin, the value of "kibanaVersion" is set to "kibana". (https://github.com/elastic/kibana/blob/master/packages/kbn-plugin-generator/template/kibana.json.ejs). 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. Got it, it's ok if the build and yarn start test pass 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. Thank you.👍 For the "kibanaVersion", probably it's not getting the version from "package.json" 🤔, because when I ran 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. Interesting, you may check @yizheliu-amazon 's build changes here - looks like you will want to change the 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. Hi Tyler, thank you for your reminder. I didn't notice there is the name change in 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 will change the "kibanaVersion" to the exact version number to avoid inputting version number manually when building through 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. Cool. Also, per the new naming convention, can you change 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. Thanks for pointing out. Sure, I just changed it in |
||
"configPath": ["opendistro_alerting"], | ||
"requiredPlugins": [], | ||
"server": true, | ||
"ui": true | ||
} |
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.
Should we bump to 1.12.0.0 ?
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.
I will do the version upgrade in another PR. Keeping the version number as 1.11 makes me possible to test the functionality in an ODFE 1.11 cluster after the migration. 😁