-
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
[Unified Integrations] Remove and cleanup add data views #115424
[Unified Integrations] Remove and cleanup add data views #115424
Conversation
…te_links_and_permissions
…te_links_and_permissions
…te_links_and_permissions
…te_links_and_permissions
…te_links_and_permissions
…te_links_and_permissions
@elasticmachine merge upstream |
merge conflict between base and head |
…er/kibana into joshdover-integrations/dover-fixes
…egrations/dover-fixes
@joshdover I merged master into your branch 4c26457 Required a few manual conflict fixes. I did a few spotchecks, and seems ok, but please verify as well. thx! |
Pinging @elastic/fleet (Team:Fleet) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
app-services code lgtm, didn't test
💚 Build SucceededMetrics [docs]Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
) Co-authored-by: cchaos <[email protected]> Co-authored-by: Dave Snider <[email protected]> Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Thomas Neirynck <[email protected]>
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
…-link-to-kibana-app * 'master' of github.com:elastic/kibana: (30 commits) Fix potential error from undefined (elastic#115562) [App Search, Crawler] Fix validation step panel padding/whitespace (elastic#115542) [Cases][Connectors] ServiceNow ITOM: MVP (elastic#114125) Change default session idle timeout to 8 hours. (elastic#115565) Upgrade EUI to v39.1.1 (elastic#114732) [App Search] Wired up organic results on Curation Suggestions view (elastic#114717) [i18n] remove i18n html extractor (elastic#115004) [Logs/Metrics UI] Add deprecated field configuration to Deprecations API (elastic#115103) [Transform] Add alerting rules management to Transform UI (elastic#115363) Update UI links to Fleet and Agent docs (elastic#115295) [ML] Adding ability to change data view in advanced job wizard (elastic#115191) Change deleteByNamespace to include legacy URL aliases (elastic#115459) [Unified Integrations] Remove and cleanup add data views (elastic#115424) [Discover] Show ignored field values (elastic#115040) [ML] Stop reading the ml.max_open_jobs node attribute (elastic#115524) [Discover] Improve doc viewer code in Discover (elastic#114759) [Security Solutions] Adds security detection rule actions as importable and exportable (elastic#115243) [Security Solution] [Platform] Migrate legacy actions whenever user interacts with the rule (elastic#115101) [Fleet] Add telemetry for integration cards (elastic#115413) 🐛 Fix single percentile case when ES is returning no buckets (elastic#115214) ... # Conflicts: # x-pack/plugins/reporting/public/management/__snapshots__/report_listing.test.tsx.snap
…115581) Co-authored-by: cchaos <[email protected]> Co-authored-by: Dave Snider <[email protected]> Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Thomas Neirynck <[email protected]> Co-authored-by: Josh Dover <[email protected]> Co-authored-by: cchaos <[email protected]> Co-authored-by: Dave Snider <[email protected]> Co-authored-by: Thomas Neirynck <[email protected]>
Hi @joshdover Under validation of Ticket : #113434, we have following observations:
Build details: Recording: Recording.16.mp4Query: Is this expected. Could you please confirm on this. Thanks |
Summary
Depends on #114911 being merged first
Fixes #94181 #113434
Checklist
Delete any items that are not applicable to this PR.
Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
For maintainers