-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Search] [Onboarding] Search api key refactor #199790
[Search] [Onboarding] Search api key refactor #199790
Conversation
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#7405[✅] x-pack/test_serverless/functional/test_suites/search/config.ts: 50/50 tests passed. |
x-pack/test_serverless/functional/test_suites/search/search_index_detail.ts
Outdated
Show resolved
Hide resolved
40a80bd
to
3f5e7c5
Compare
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.
Overall this is a good improvement.
before(async () => { | ||
await es.index({ | ||
index: indexName, | ||
refresh: 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.
not sure this is enough of a fix, we probably want to leave this skipped until we can so a larger refactor on these tests.
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.
As I've got the test was flaky because when we update data this appear in kibana in random moment and makes test flaky. So I hope this one will permanently fix it
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.
await pageObjects.svlApiKeys.expectAPIKeyAvailable(); | ||
const apiKey = await pageObjects.svlApiKeys.getAPIKeyFromUI(); | ||
await pageObjects.svlSearchIndexDetailPage.expectAPIKeyToBeVisibleInCodeBlock(apiKey); | ||
describe('API key details', () => { |
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 is ok, but I'd actually like to see us move these and the start page API key tests into a different file so that we can tag them to skip if they continue to be flakey.
@elasticmachine merge upstream |
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#7467[❌] x-pack/test_serverless/functional/test_suites/search/config.ts: 70/105 tests passed. |
…na into search-api-key-refactor
if the user is a viewer, they should see the "cannot create API key, no permissions" message. Currently allows you to create an API Key and the validaty check also throws an exception
Not sure why we dont have a FTR test for this. Could you check? Checked the other scenarios:
|
…na into search-api-key-refactor
017845b
to
7a47972
Compare
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
History
|
Refactor search api key - get rid from useReduces - simplify logic in provider - create request hooks - fix multiple initialization --------- Co-authored-by: Elastic Machine <[email protected]>
Refactor search api key