Skip to content
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

Triggers action ui x-pack configuration error #64920

Closed
cnasikas opened this issue Apr 30, 2020 · 4 comments
Closed

Triggers action ui x-pack configuration error #64920

cnasikas opened this issue Apr 30, 2020 · 4 comments
Labels
estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) technical debt Improvement of the software architecture and operational architecture

Comments

@cnasikas
Copy link
Member

Hi everyone!

I get the following error:

  log   [14:22:36.213] [fatal][root] { Error: Unknown configuration key(s): "xpack.triggers_actions_ui.enabled". Check for spelling errors and ensure that expected plugins are installed.
    at ensureValidConfiguration (/Users/laxmana/workspace/kibana/src/core/server/legacy/config/ensure_valid_configuration.ts:41:11) code: 'InvalidConfig', processExitCode: 64, cause: undefined }
 FATAL  Error: Unknown configuration key(s): "xpack.triggers_actions_ui.enabled". Check for spelling errors and ensure that expected plugins are installed.

Inside my kibana.dev.yml I have xpack.triggers_actions_ui.enabled: true

Thanks!

@cnasikas cnasikas added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Apr 30, 2020
@mikecote
Copy link
Contributor

Looks like there's no config object in the plugin after migrating to Kibana Platform. To be investigated as any plugin in Kibana should support being disabled.

@YulNaumenko YulNaumenko added the technical debt Improvement of the software architecture and operational architecture label Mar 11, 2021
@gmmorris
Copy link
Contributor

gmmorris commented Jul 2, 2021

@mikecote - is any work actually needed here? Isn't this just the nature of how Kibana Platform works?

@mikecote
Copy link
Contributor

mikecote commented Jul 5, 2021

@gmmorris I think the question becomes "should the UI plugin be disableable?". We're already discussing "no" here for the alerting plugin which may result in the same for the UI plugin.

@gmmorris gmmorris added the loe:needs-research This issue requires some research before it can be worked on or estimated label Jul 15, 2021
@YulNaumenko
Copy link
Contributor

Closing in favor of removing configuration

@gmmorris gmmorris added the estimate:needs-research Estimated as too large and requires research to break down into workable issues label Aug 18, 2021
@gmmorris gmmorris removed the loe:needs-research This issue requires some research before it can be worked on or estimated label Sep 2, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) technical debt Improvement of the software architecture and operational architecture
Projects
None yet
Development

No branches or pull requests

5 participants