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.
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
[SLO] [Alerting] deployment agnostic slo burn rate rule tests #187924
[SLO] [Alerting] deployment agnostic slo burn rate rule tests #187924
Changes from 8 commits
f495936
95feb99
647e38b
4876a31
2ee040b
f28913a
fb4d553
f1d7143
7d70b1a
390ebb6
ad12156
c02f861
145ed27
6ee3000
d43a0c7
34fc89c
770101b
9356c2a
65e4e17
4978fe7
b7ae99a
1facfd1
dea02c6
0be3024
7053b2b
daa1b8f
9b76f4f
c4cfa24
5f9ae2c
7dd2649
52ecd8d
dd8ee61
ea47dbf
0a2b008
91a4511
364eea3
c3f0329
85273a2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
supertest
is initialized withoperator
user and its Cookie persist. Passing custom api key for specific role has no affect, API call will be executed withoperator
privileges.If you test the APIs, it is critical to use
supertestWithoutAuth
only. If it is env cleanup andadmin
has no permissions to delete, usingsupertest
is reasonable but not need to pass api key.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.
these tags has no affect. We don't use any custom tagging because tests in
deployment_agnostic/
path are assumed to be compatible for both stateful and serverless.You just need to load test in both stateful and serverless FTR configs.
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.
Awesome!
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.
Same here. Please use only
supertestWithoutAuth
to make API call with api key for the specified roleThere 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 think this service can be used as an example to make quick changes https://github.com/elastic/kibana/blob/main/x-pack/test/api_integration/deployment_agnostic/services/slo_api.ts
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.
Not every service in
'../../../common/services'
is deployment-agnostic and we shouldn't import it like this.Instead I picked up the ones that work both in serverless/stateful and import as
deploymentAgnosticServices
If you need any other services from
common/services
let me know which ones so I can review/modify it and load inkibana/x-pack/test/api_integration/deployment_agnostic/services/deployment_agnostic_services.ts
Lines 15 to 28 in 145ed27