-
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
[Saved Objects] Import SO types from server
rather than common
to avoid deprecation
#149289
[Saved Objects] Import SO types from server
rather than common
to avoid deprecation
#149289
Conversation
725af0e
to
cd0806d
Compare
…objects-api-server
Pinging @elastic/kibana-core (Team:Core) |
Pinging @elastic/fleet (Team:Fleet) |
Pinging @elastic/uptime (Team:uptime) |
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.
Fleet changes 🚀
@@ -7,7 +7,7 @@ | |||
*/ | |||
|
|||
import { isNotFoundFromUnsupportedServer } from '@kbn/core-elasticsearch-server-internal'; | |||
import type { SavedObject } from '@kbn/core-saved-objects-common'; |
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.
Yeah... It kinda awkward having to do this to avoid the deprecation, given both types are supposed to be the same, but if that's the direction we're willing to take, I guess it's fine.
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.
ResponseOps changes LGTM!
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.
Visualizations team changes LGTM
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.
These changes look fine. Is the plan to remove the declarations in common entirely in the next major version release?
* main: (54 commits) [APM] Allow calling `createInternalESClient` without `context` (elastic#149320) [Synthetics] Errors list active state (elastic#149387) [FTRs] Execution Context: fix no data flakiness (elastic#149406) [Cloud Posture] - Deprecate csp rule remove migration object (elastic#148530) Bump elasticsearch-js to 8.6.0-canary.3 (elastic#148521) [Fleet] Use optimistic locking when updating `installed_es` on input package policy creation (elastic#148883) [ML] Remove job_type from job definitions in modules (elastic#149247) [ML] Consolidate `query_utils` into package `@kbn/ml-query-utils` (elastic#149224) [Synthetics] Better formatting for waterfall timeline tooltips (elastic#149142) [Cloud Posture] CIS AWS support - changes to findings tables (elastic#148945) [Lens] Enable previous time shift when using a date histogram (elastic#149126) [Synthetics] Object types panel and thresholds (elastic#149099) [Fleet] added back batch exec for update tags (elastic#148618) 148790 - Fix scroll style for setup guide flyout (elastic#149242) Fix a11y issue with dev tool tabs (elastic#149349) [APM] Fix mobile indices (elastic#149230) [Dashboard] Fix Phrase_filter query for scripted fields (elastic#148942) (elastic#148943) renderCustomActionsRow with named params instead of args (elastic#149304) [ML] Adding ML execution context to es requests (elastic#148746) [Custom Branding] Replace EuiLoadingElastic with EuiLoadingSpinner (elastic#149261) ...
@jloleysens FYI I ran into some circular references between the |
💚 Build Succeeded
Metrics [docs]Unknown metric groupsReferences to deprecated APIs
History
To update your PR or re-run it, just comment with: cc @jloleysens |
Summary
After merging #148979 there are a number of imports that can be fixed immediately to address our new deprecation notice.
To Core reviewers
The package
core-saved-objects-server
is using types fromcore-saved-objects-api-server
which creates a circular dependency when usingSavedObject
type from it's new home incore-saved-object-server
:core-saved-objects-server
->core-saved-objects-api-server
->core-saved-objects-server
One solution is that we can create a new package
packages/core/saved-objects/core-saved-objects-server-shared
that will only hold theSavedObject
type and a select few others. I'm not sure what the best approach here is. I have leftcore-saved-objects-api-server
unchanged for now (i.e., it is still importingSavedObject
fromcommon
which is deprecated).Any input would be greatly appreciated!