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

Reassign ownership of plugins/saved_objects away from Core team #46435

Open
2 of 20 tasks
rudolf opened this issue Sep 24, 2019 · 23 comments
Open
2 of 20 tasks

Reassign ownership of plugins/saved_objects away from Core team #46435

rudolf opened this issue Sep 24, 2019 · 23 comments
Assignees
Labels
Feature:NP Migration loe:small Small Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@rudolf
Copy link
Contributor

rudolf commented Sep 24, 2019

The SavedObject class and other helpers from the savedObjects plugin in src/plugins/saved_objects/ is technical debt left over from before the NP migration and will be removed in 8.0. The following features/utilities will have to be migrated:

  • Before saving, checks for any existing saved object with the same type and title. If found, prompt users if they want to overwrite the existing object instead of saving a new one.
    -> Move to src/plugins/kibana_react/public/saved_objects/saved_object_save_modal.tsx
  • if showInRecentlyAccessed is set to true, updates the recentlyAccessed menu/list
    -> Use chrome.recentlyAccessed api explicitly when needed
  • injectReferences / extractReferences temporary compatibility helpers to help plugins migrate to references
    -> Plugins should complete the migration to references by using references directly
  • Stop depending on savedObjects:listingLimit advanced setting. Users sometimes sets this to 10k which adversely affects Elasticsearch performance Expensive queries are causing unnecessary load and delays on Elasticsearch  #93770. We need a UI pattern that scales better see [EuiPagination] add a variation with next/previous buttons only eui#4506 (will open separate issue)

Plugins that have savedObjects as a requiredPlugin or requiredBundle and require action:

@rudolf rudolf added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:New Platform Team:AppArch labels Sep 24, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-arch

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform

@rudolf rudolf changed the title NP Migration: ui/saved_object NP Migration: ui/saved_objects/saved_object Sep 24, 2019
This was referenced Sep 24, 2019
@joshdover
Copy link
Contributor

Moving to App Team after discussing them taking this on.

@joshdover joshdover added Feature:NP Migration Team:Visualizations Visualization editors, elastic-charts and infrastructure and removed Feature:New Platform Team:AppArch Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc labels Oct 15, 2019
@joshdover
Copy link
Contributor

\cc @flash1293

@joshdover
Copy link
Contributor

@kertal just to confirm, this is still blocked by #42639?

@kertal
Copy link
Member

kertal commented Jan 29, 2020

No, due to recent changes this can be started

@joshdover
Copy link
Contributor

@maryia-lapata Did #57452 close this issue as well?

@flash1293
Copy link
Contributor

@joshdover This is not completely done, we just moved the code over for now. We will continue cleaning up the implementation in the upcoming weeks.

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@planadecu planadecu added the loe:small Small Level of Effort label Feb 8, 2022
@afharo afharo added EnableJiraSync and removed Team:Visualizations Visualization editors, elastic-charts and infrastructure Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc EnableJiraSync labels Feb 8, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Feb 8, 2022
@afharo afharo added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Feb 8, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Feb 8, 2022
@afharo afharo added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Feb 8, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)

@rudolf
Copy link
Contributor Author

rudolf commented Feb 14, 2022

  1. @elastic/kibana-presentation is tracking removing their dependency on the SavedObjectsLoader here [Dashboard] [Meta] Tech Debt Roadmap #120182 "Using the saved objects client directly".

  2. Once that is done, we can remove the tagging decorator from the saved_objects_tagging_oss plugin so that this plugin no longer depends on plugins/saved_objects.

  3. The remaining dependencies should be limited to the SavedObjectClass and the UI components like SavedObjectSaveModal, SavedObjectFinder and misc helpers. These should either be maintained by the wider Kibana analytics team (the main consumer) or shared UX team.

@rudolf
Copy link
Contributor Author

rudolf commented Mar 9, 2023

We've set a deadline for removing this plugin for 8.0 and then extended it by another year to 8.8. The important thing is that the core team is not maintaining this and our ownership of this plugin does not make sense. So instead of removing it completely we can just remove our ownership. I've asked @thomasneirynck to help us find the most suitable team to own this past 8.8.

@rudolf rudolf changed the title Remove plugins/saved_objects Reassign ownership of plugins/saved_objects away from Core team Mar 9, 2023
@rudolf
Copy link
Contributor Author

rudolf commented Mar 14, 2023

Related #150604

@stratoula stratoula removed the Team:Visualizations Visualization editors, elastic-charts and infrastructure label May 30, 2023
@thomasneirynck
Copy link
Contributor

thomasneirynck commented Jan 11, 2024

After some auditing and cleanup, it seems the dependencies are as follows

  1. Analyticss-app no longer have plugin dependencies, but retains some static dependencies on the save_modal-UX.
  2. there is a plugin-dependency for the class still in saved_objects_tagging_oss.
    savedObjects.registerDecorator(tagDecoratorConfig);
  3. security_solution likely has an unused dependency here ( ) cc @YulNaumenko This probably can be removed, but will need double checking.

wrt future ownership: it seems current dependencies are minimal, and saved_modal could probably move to a package. The actual class and decorator might be something that shared-ux or core retain until that last dependency is cleaned up.

cc @lukeelmers @rudolf @vadimkibana wdyt?

@TinaHeiligers
Copy link
Contributor

@thomasneirynck is this issue still valid?

@thomasneirynck
Copy link
Contributor

@TinaHeiligers yes, it still is.

@YulNaumenko
Copy link
Contributor

After some auditing and cleanup, it seems the dependencies are as follows

  1. Analyticss-app no longer have plugin dependencies, but retains some static dependencies on the save_modal-UX.
  2. there is a plugin-dependency for the class still in saved_objects_tagging_oss.
    savedObjects.registerDecorator(tagDecoratorConfig);
  3. security_solution likely has an unused dependency here (
    ) cc @YulNaumenko This probably can be removed, but will need double checking.

wrt future ownership: it seems current dependencies are minimal, and saved_modal could probably move to a package. The actual class and decorator might be something that shared-ux or core retain until that last dependency is cleaned up.

cc @lukeelmers @rudolf @vadimkibana wdyt?

It should be removed for security_solution. We used that before for Discover integration and don't need that any more. Just forgotten to cleanup.

YulNaumenko added a commit that referenced this issue Apr 12, 2024
rudolf added a commit that referenced this issue Sep 20, 2024
## Summary

Another step towards getting rid of the savedobjects plugin which was
scheduled for removal since 2019 😓
#46435


### Checklist

Delete any items that are not applicable to this PR.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [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
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This renders correctly on smaller devices using a responsive
layout. (You can test this [in your
browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)


### 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:

| Risk | Probability | Severity | Mitigation/Notes |

|---------------------------|-------------|----------|-------------------------|
| Multiple Spaces—unexpected behavior in non-default Kibana Space.
| Low | High | Integration tests will verify that all features are still
supported in non-default Kibana Space and when user switches between
spaces. |
| Multiple nodes—Elasticsearch polling might have race conditions
when multiple Kibana nodes are polling for the same tasks. | High | Low
| Tasks are idempotent, so executing them multiple times will not result
in logical error, but will degrade performance. To test for this case we
add plenty of unit tests around this logic and document manual testing
procedure. |
| Code should gracefully handle cases when feature X or plugin Y are
disabled. | Medium | High | Unit tests will verify that any feature flag
or plugin combination still results in our service operational. |
| [See more potential risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |


### For maintainers

- [ ] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

---------

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
Feature:NP Migration loe:small Small Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests