[ResponseOps] consider making some plugin config available in the UX via Advanced Settings #132183
Labels
Feature:Actions/Framework
Issues related to the Actions Framework
Feature:Alerting/RulesFramework
Issues related to the Alerting Rules Framework
Feature:Task Manager
research
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
The alerting, actions, and task_manager plugins have a lot of configuration options:
config code from the plugins
kibana/x-pack/plugins/alerting/server/config.ts
Lines 12 to 64 in c93afa0
kibana/x-pack/plugins/actions/server/config.ts
Lines 19 to 120 in c93afa0
kibana/x-pack/plugins/task_manager/server/config.ts
Lines 24 to 146 in c93afa0
During a retrospective, it was noted that keeping all the meta-data around the config up-to-date is a chore. We have keys that are allowed to be used as env vars in Docker in one file, an allow-list for cloud usage in another file in another repo, and asciidoc documentation in several places, some duplicated between cloud and Kibana docs.
One thought was to try to move some of this configuration so that it could be edited "live", via Advanced Settings (AS).
pros:
cons:
I think we'd need to do the following:
enabledActionTypes
would make sense, to prevent some connectors from being used in some spacesThe text was updated successfully, but these errors were encountered: