-
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
[Alerting][Connectors] Import rules and connectors #94152
Comments
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
Blocked by #94106 |
From this comment, it would be nice to add something to the import warning if imported connectors have a higher license level than current Kibana uses. |
Importing the connectors with the higher license than the current user have, could be OK if we add the warning message after the import, but for the rules it can cause some noise, which is probably OK too. |
Based on this comment, we should check for the existence of security rules (producer: |
This issue covers the import portion of importing/exporting rules and connectors. We want to be able to import rules and connectors from the saved object management page.
Refer to this PR for details about setting warnings within the
onImport
hook1. Import rules
Add an
onImport
hook that sets a warning on the import flyout when rules are imported. This should reset theexecutionStatus
topending
and update theupdatedAt
field to the current time.2. Import connectors
Add an
onImport
hook that sets a warning on the import flyout when connectors are imported### 3. Audit log entry for importsBased on this comment and the ensuring discussion, we should be generating alerting/action specific audit log entries on import so the imports don't just show up as generic saved object actions.
Removed #3 based on this discussion in the export PR
The text was updated successfully, but these errors were encountered: