-
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
SKA: Relocate @kbn/core
inside src/core/packages/core
#205036
base: main
Are you sure you want to change the base?
SKA: Relocate @kbn/core
inside src/core/packages/core
#205036
Conversation
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
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.
LGTM! Let's see if this change has the effect we expect.
I noticed many (previously) broken links. I wouldn't update them here to reduce the PR codereview impact.
dev_docs/tutorials/saved_objects.mdx
Outdated
@@ -14,7 +14,7 @@ The folder should contain a file per type, named after the snake_case name of th | |||
**src/plugins/my_plugin/server/saved_objects/dashboard_visualization.ts** | |||
|
|||
```ts | |||
import { SavedObjectsType } from 'src/core/server'; | |||
import { SavedObjectsType } from 'src/core/packages/core/server'; |
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.
All the imports here should actually be @kbn/core/server
(or the individual saved-objects package)
legacy_rfcs/text/0015_bazel.md
Outdated
@@ -76,7 +76,7 @@ A Bazel [macro](https://docs.bazel.build/versions/master/skylark/macros.html) wi | |||
|
|||
A Bazel [macro](https://docs.bazel.build/versions/master/skylark/macros.html) will be created to centralize the usage of Webpack. The macro will, at minimum, accept a configuration file and supply a base `webpack.config.js` file. Currently, all plugins share the same Webpack configuration. Allowing a plugin to provide additional configuration will allow plugins the ability to add loaders without affecting the performance of others. | |||
|
|||
While running Kibana from source in development, the proxy server will ensure that client-side code for plugins is compiled and available. This is currently handled by the [basePathProxy](https://github.com/elastic/kibana/blob/main/src/core/server/http/base_path_proxy_server.ts), where server restarts and optimizer builds are observed and cause the proxy to pause requests. With Bazel, we will utilize [iBazel](https://github.com/bazelbuild/bazel-watche) to watch for file changes and re-build the plugin targets when necessary. The watcher will emit [events](https://github.com/bazelbuild/bazel-watcher#remote-events) that we will use to block requests and provide feedback to the logs. | |||
While running Kibana from source in development, the proxy server will ensure that client-side code for plugins is compiled and available. This is currently handled by the [basePathProxy](https://github.com/elastic/kibana/blob/main/src/core/packages/core/server/http/base_path_proxy_server.ts), where server restarts and optimizer builds are observed and cause the proxy to pause requests. With Bazel, we will utilize [iBazel](https://github.com/bazelbuild/bazel-watche) to watch for file changes and re-build the plugin targets when necessary. The watcher will emit [events](https://github.com/bazelbuild/bazel-watcher#remote-events) that we will use to block requests and provide feedback to the logs. |
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.
this path is no-longer working (it didn't work before this PR anyways) 🫠
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.
I'll exclude all changes in legacy_rfcs
@@ -67,7 +67,7 @@ export interface AppMountParameters<HistoryLocationState = unknown> { | |||
* import ReactDOM from 'react-dom'; | |||
* import { Router, Route } from 'react-router-dom'; | |||
* | |||
* import { CoreStart, AppMountParameters } from 'src/core/public'; | |||
* import { CoreStart, AppMountParameters } from 'src/core/packages/core/public'; |
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.
@kbn/core/public
@@ -20,12 +20,12 @@ export interface DeprecationDetailsMessage { | |||
export interface BaseDeprecationDetails { | |||
/** | |||
* The title of the deprecation. | |||
* Check the README for writing deprecations in `src/core/server/deprecations/README.mdx` | |||
* Check the README for writing deprecations in `src/core/packages/core/server/deprecations/README.mdx` |
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.
I doubt this link worked 🫠
@@ -58,7 +58,7 @@ export class HomePageObject extends FtrService { | |||
} | |||
|
|||
async isWelcomeInterstitialDisplayed() { | |||
// This element inherits style defined {@link https://github.com/elastic/kibana/blob/v8.14.3/src/core/public/styles/core_app/_mixins.scss#L72|here} | |||
// This element inherits style defined {@link https://github.com/elastic/kibana/blob/v8.14.3/src/core/packages/core/public/styles/core_app/_mixins.scss#L72|here} |
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.
we are not backporting to v8.14.3 😬
click Collectors "https://github.com/elastic/kibana/tree/main/src/core/packages/core/server/metrics/collectors" | ||
click OpsMetricsObservable "https://github.com/elastic/kibana/blob/92a8636f0ff63ab072527574e96e6616327b2ea4/src/core/packages/core/server/metrics/metrics_service.ts#L32" |
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.
click Collectors "https://github.com/elastic/kibana/tree/main/src/core/packages/core/server/metrics/collectors" | |
click OpsMetricsObservable "https://github.com/elastic/kibana/blob/92a8636f0ff63ab072527574e96e6616327b2ea4/src/core/packages/core/server/metrics/metrics_service.ts#L32" | |
click Collectors "https://github.com/elastic/kibana/tree/main/src/core/server/metrics/collectors" | |
click OpsMetricsObservable "https://github.com/elastic/kibana/blob/92a8636f0ff63ab072527574e96e6616327b2ea4/src/core/server/metrics/metrics_service.ts#L32" |
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.
I'm actually moving the server
folder, so I think the 1st line is correct? I'll revert changes in the second.
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.
My point is that src/core/metrics
don't exist since we moved the service to a package. But we forgot to update this reference.
I'd prefer to update these already broken URLs in a separate PR to avoid making too much noise in this important PR.
@@ -85,6 +85,6 @@ export const deprecations = ({ | |||
// vice versa. | |||
// ^ These deprecations should only be shown if they are explicitly configured for monitoring -- we should not show Monitoring | |||
// deprecations for these settings if they are inherited from the Core elasticsearch settings. | |||
// See the Core implementation: src/core/server/elasticsearch/elasticsearch_config.ts | |||
// See the Core implementation: src/core/packages/core/server/elasticsearch/elasticsearch_config.ts |
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.
Old path was still broken... let's minimize noise.
// See the Core implementation: src/core/packages/core/server/elasticsearch/elasticsearch_config.ts | |
// See the Core implementation: src/core/server/elasticsearch/elasticsearch_config.ts |
@@ -29,7 +29,7 @@ These surface runtime deprecations, e.g. a Painless script that uses a deprecate | |||
request to a deprecated API. These are also generally surfaced as deprecation headers within the | |||
response. Even if the cluster state is good, app maintainers need to watch the logs in case | |||
deprecations are discovered as data is migrated. Starting in 7.x, deprecation logs can be written to a file or a data stream ([#58924](https://github.com/elastic/elasticsearch/pull/58924)). When the data stream exists, the Upgrade Assistant provides a way to analyze the logs through Observability or Discover ([#106521](https://github.com/elastic/kibana/pull/106521)). | |||
* [**Kibana deprecations API.**](https://github.com/elastic/kibana/blob/main/src/core/server/docs/kib_core_deprecations_service.mdx) This is information about deprecated features and configs in Kibana. These deprecations are only communicated to the user if the deployment is using these features. Kibana engineers are responsible for adding deprecations to the deprecations API for their respective team. | |||
* [**Kibana deprecations API.**](https://github.com/elastic/kibana/blob/main/src/core/packages/core/server/docs/kib_core_deprecations_service.mdx) This is information about deprecated features and configs in Kibana. These deprecations are only communicated to the user if the deployment is using these features. Kibana engineers are responsible for adding deprecations to the deprecations API for their respective team. |
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.
👍
2a25ad1
to
a11d70f
Compare
Pinging @elastic/kibana-core (Team:Core) |
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.
codeowner changes lgtm
0a5657f
to
d7e122e
Compare
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.
LGTM (relocation of src/core/packages/core/server/integration_tests/config/check_dynamic_config.test.ts
)
d7e122e
to
d9b8cfc
Compare
d9b8cfc
to
bb393a9
Compare
…t --include-path /api/status --include-path /api/alerting/rule/ --include-path /api/alerting/rules --include-path /api/actions --include-path /api/security/role --include-path /api/spaces --include-path /api/fleet --include-path /api/dashboards --update'
💔 Build Failed
Failed CI StepsMetrics [docs]Public APIs missing exports
Unknown metric groupsReferences to deprecated APIs
History
|
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.
SCSS checked
Summary
We want to relocate all of
packages/core/**
modules insidesrc/core/packages
, and we believe some tooling (e.g. build_api_docs) might not like the fact that we're creating apackages
folder inside the@kbn/core
package folder.This PR is an attempt at moving it within packages, as the title describes. cc @afharo