-
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
[WIP][skip-ci] Retrieve index pattern from ingest manager app #60063
Closed
jonathan-buttner
wants to merge
445
commits into
elastic:master
from
jonathan-buttner:get-ip-from-ingest
Closed
[WIP][skip-ci] Retrieve index pattern from ingest manager app #60063
jonathan-buttner
wants to merge
445
commits into
elastic:master
from
jonathan-buttner:get-ip-from-ingest
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* plugin.start now does reactdom.render vs returning react element export plugin function from public/index * Move setClient call from plugin.start to plugin.setup * Use `useUiSetting$` from `useKibana` hooks
Can't use useKibana outside a React component. Reverting to prior approach since it's still NP. Can revisit context usage in a followup PR
* Support basic "click button -> show spinner -> installed" install flow * Remove incorrect comments. Add TS return types to data functions.
* Use NP feature_catalogue.register * Use type from NP plugin
…ana into feature-ingest
This reverts commit d05f20d.
* Update (all remaining?) references from integrations_manager to EPM * Update path in i18n file
* change min max version to single range value * add elastic stack icon and change text * remove badge from version and use code font * remove euistyled * add back version component lost in merge * remove euiStyled * remove old file
Temporary work around until we know how the stack wants to add the permissions we need. Either adding to the kibana user or creating a new user.
This reverts commit f1020e4.
Temporary work around until we know how the stack wants to add the permissions we need. Either adding to the kibana user or creating a new user.
* Initialize es in test. * Add it(), no es.init() * Clean up.
* add confirmation modal, move install state to Header * update callout to use title * move components only used in detail view to detail dir * use better variable names * update to more descriptive variable names
…51252) Discussed this with @skh elastic#51112 (comment) & elastic#51112 (comment) as well as in a video call Also added some TS type annotations for data fetching functions to make the contracts more explicit
…stic#51414) * API only shows installable assets. Server types to own file. Restore enums * Fix type imports * Only return installable asset types (kibana for now) * server/types now only has code from hapi which shouldn't go to client * Add more restricted TS types to DisplayAssets object * Flip order of arguments to Extract In these cases it still works the same, but looking at https://www.typescriptlang.org/docs/handbook/advanced-types.html the signature is `Extract<T, U>` - Extract from `T` those types that are assignable to `U` so the larger set should be first
* Disable create/destroy CTAs if no write capability Use `core.application.capabilities.ingestManager.write` to test user permissions * Add -all & -read tags for HTTP routes * Update test .expect() to match description * Add useCapabilities hook. Fix two issues with hiding/disabling CTA. Co-authored-by: Elastic Machine <[email protected]>
FTR tests failing to start ES with error ``` ERROR ERROR: setting [xpack.security.authc.api_key.enabled] already set, saw [true] and [true] ``` https://github.com/elastic/kibana/pull/59376/checks?check_run_id=503930031 & https://github.com/elastic/kibana/pull/59376/checks?check_run_id=503975576 etc It appears the xpack.security.authc.api_key.enabled flag was recently added to master in another part, so remove our instance of the setting to prevent the error
These should have failed when the routes were changed. Will go back and see what happened.
* Add revision to agent config and datasource saved objects, add delete datasource service and datasource * Add revision to full agent config output * PR feedback
💔 Build FailedTest FailuresKibana Pipeline / x-pack-intake-agent / X-Pack Jest Tests.x-pack/plugins/endpoint/server/routes/resolver/queries.related events query generates the correct legacy queriesStandard Out
Stack Trace
Kibana Pipeline / x-pack-intake-agent / X-Pack Jest Tests.x-pack/plugins/endpoint/server/routes/resolver/queries.related events query generates the correct non-legacy queriesStandard Out
Stack Trace
Kibana Pipeline / x-pack-intake-agent / X-Pack Jest Tests.x-pack/plugins/endpoint/server/routes/resolver/queries.children events query generates the correct legacy queriesStandard Out
Stack Trace
and 6 more failures, only showing the first 3. To update your PR or re-run it, just comment with: |
FYI, |
Thanks @jen-huang I'll switch it over! |
Closing because commits from feature-ingest aren't syncing up. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR connects the endpoint and ingest apps. The endpoint app will rely on the ingest manager to retrieve the index pattern for querying elasticsearch. The index pattern is built using the contents of the endpoint package.
One issue I think I'm going to run into is that the ingest manager's setup doesn't happen until the app is navigated too in the UI. The endpoint package needs to be installed by default and be there before the endpoint app can start making queries to elasticsearch. I think the ingest manager will need to do install the default system packages earlier or the endpoint app will have to call the
setup
route first.