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

[RAM] Use AAD When Running Action #161213

Closed
wants to merge 26 commits into from

Conversation

jcger
Copy link
Contributor

@jcger jcger commented Jul 4, 2023

Summary

Closes #160838

Feature can be activated via feature flag:
xpack.trigger_actions_ui.enableExperimental: ['isMustacheAutocompleteOn', 'showMustacheAutocompleteSwitch']

@jcger jcger added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v8.10.0 labels Jul 4, 2023
producerId="alerting"
/>
</KibanaReactContext.Provider>
<QueryClientProvider client={queryClient}>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like the plugin isn't importing the ActionForm but just this test so we will keep React Query as it is

@kibana-ci
Copy link
Collaborator

kibana-ci commented Sep 26, 2023

💔 Build Failed

Failed CI Steps

Test Failures

  • [job] [logs] Investigations - Security Solution Cypress Tests #6 / Detections : Page Filters Impact of inputs "after each" hook for "should take timeRange into account" "after each" hook for "should take timeRange into account"
  • [job] [logs] Investigations - Security Solution Cypress Tests #6 / Detections : Page Filters Impact of inputs should take timeRange into account should take timeRange into account
  • [job] [logs] FTR Configs #8 / Discover alerting Search source Alert "after all" hook for "should check that there are no errors detected after an alert is created"
  • [job] [logs] FTR Configs #8 / Discover alerting Search source Alert "after all" hook for "should check that there are no errors detected after an alert is created"
  • [job] [logs] FTR Configs #8 / Discover alerting Search source Alert should show time field validation error
  • [job] [logs] FTR Configs #8 / Discover alerting Search source Alert should show time field validation error
  • [job] [logs] FTR Configs #58 / serverless common UI Index Management Indices "before all" hook for "renders the indices tab"
  • [job] [logs] FTR Configs #58 / serverless observability UI landing page "before all" hook for "has quickstart badge"
  • [job] [logs] FTR Configs #33 / serverless security UI landing page "before all" hook for "has serverless side nav"

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
stackConnectors 239 206 -33
triggersActionsUi 586 591 +5
total -28

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id before after diff
alerting 741 742 +1
triggersActionsUi 551 553 +2
total +3

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
stackConnectors 467.0KB 449.3KB -17.7KB
triggersActionsUi 1.4MB 1.4MB +1.7KB
total -16.1KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
stackConnectors 36.5KB 36.2KB -326.0B
triggersActionsUi 92.0KB 98.6KB +6.6KB
total +6.3KB
Unknown metric groups

API count

id before after diff
alerting 772 773 +1
triggersActionsUi 577 579 +2
total +3

ESLint disabled line counts

id before after diff
stackConnectors 94 93 -1
triggersActionsUi 124 125 +1
total -0

Total ESLint disabled count

id before after diff
stackConnectors 99 98 -1
triggersActionsUi 130 131 +1
total -0

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@mdefazio
Copy link
Contributor

mdefazio commented Oct 17, 2023

@jcger @XavierM Perhaps a repeated question, so apologies upfront.

What is our reasoning for putting this inside the action? And not above all actions? Assuming I will need to toggle this for every action I add?

Had we previously discussed placing this within the variables popover? Was there a reason not to do this? Update: Realizing now why this is not a good idea...

image

@mdefazio
Copy link
Contributor

@lcawl Would you mind taking a look at this copy? (And I didn't know if we should provide an example of how to access these fields...and what that example looks like)

cc/ @XavierM

Screenshot--2023-10-17--Designs - System Actions

@Zacqary Zacqary self-assigned this Oct 25, 2023
@Zacqary
Copy link
Contributor

Zacqary commented Oct 25, 2023

Picking this up. TODO:

  • Add tests
  • Save the previous template message in memory when the user toggles on AAD mode
  • Investigate how many stack connectors use multiple message variables, and ensure they're all toggling correctly (e.g. Subject line and message body for email, Jira summary and message, ServiceNow summary and message)

@Zacqary
Copy link
Contributor

Zacqary commented Oct 30, 2023

Closing in favor of #170162

@Zacqary Zacqary closed this Oct 30, 2023
Zacqary added a commit that referenced this pull request Nov 14, 2023
## Summary

Reopen of #161213

Closes #160838

Feature can be activated via feature flag:
`xpack.trigger_actions_ui.enableExperimental:
['isMustacheAutocompleteOn', 'showMustacheAutocompleteSwitch']`
<img width="605" alt="Screenshot 2023-10-30 at 5 52 39 PM"
src="https://github.com/elastic/kibana/assets/1445834/da24b419-3b08-4014-be2f-99692773755f">
<img width="583" alt="Screenshot 2023-10-30 at 5 52 22 PM"
src="https://github.com/elastic/kibana/assets/1445834/fc5b8a1e-8202-4491-b4fb-694b70809f4d">



### Checklist

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

---------

Co-authored-by: Julian Gernun <17549662+jcger@users.noreply.github.com>
Co-authored-by: Xavier Mouligneau <xavier.mouligneau@elastic.co>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
jillguyonnet pushed a commit to jillguyonnet/kibana that referenced this pull request Nov 16, 2023
## Summary

Reopen of elastic#161213

Closes elastic#160838

Feature can be activated via feature flag:
`xpack.trigger_actions_ui.enableExperimental:
['isMustacheAutocompleteOn', 'showMustacheAutocompleteSwitch']`
<img width="605" alt="Screenshot 2023-10-30 at 5 52 39 PM"
src="https://github.com/elastic/kibana/assets/1445834/da24b419-3b08-4014-be2f-99692773755f">
<img width="583" alt="Screenshot 2023-10-30 at 5 52 22 PM"
src="https://github.com/elastic/kibana/assets/1445834/fc5b8a1e-8202-4491-b4fb-694b70809f4d">



### Checklist

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

---------

Co-authored-by: Julian Gernun <17549662+jcger@users.noreply.github.com>
Co-authored-by: Xavier Mouligneau <xavier.mouligneau@elastic.co>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v8.10.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[RAM] Update the platform to allow actions to query directly the alert as data
6 participants