-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
add cGroupOverrides to the legacy config #77180
add cGroupOverrides to the legacy config #77180
Conversation
Pinging @elastic/kibana-platform (Team:Platform) |
ops.cGroupOverrides.cpuPath | ||
ops.cGroupOverrides.cpuAcctPath | ||
cpu.cgroup.path.override | ||
cpuacct.cgroup.path.override |
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 added the new ones, but also kept the deprecated name to avoid a breaking change
src/legacy/server/config/schema.js
Outdated
@@ -144,6 +144,7 @@ export default () => | |||
|
|||
ops: Joi.object({ | |||
interval: Joi.number().default(5000), | |||
cGroupOverrides: HANDLED_IN_NEW_PLATFORM, |
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 can probably remove old the schema up on lines 52-66 now?
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.
Right. I had to add the explicit definition in ops
though, as
kibana/src/legacy/server/status/lib/metrics.js
Lines 119 to 120 in c528f24
cpuPath: this.config.get('ops.cGroupOverrides.cpuPath'), | |
cpuAcctPath: this.config.get('ops.cGroupOverrides.cpuAcctPath'), |
is throwing error when trying to access the property if the schema is undefined (which make sense, HANDLED_IN_NEW_PLATFORM
is only meant to be used for config values that are ONLY used in KP)
💚 Build SucceededBuild metrics
History
To update your PR or re-run it, just comment with: |
* add cGroupOverrides to the legacy config * update missing usages * remove old cpu/cgroup schema
…s-for-710 * 'master' of github.com:elastic/kibana: (65 commits) Separate url forwarding logic and legacy services (elastic#76892) Bump yargs-parser to v13.1.2+ (elastic#77009) [Ingest Manager] Shared Fleet agent policy action (elastic#76013) [Search] Re-add support for aborting when a connection is closed (elastic#76470) [Search] Remove long-running query pop-up (elastic#75385) [Monitoring] Fix UI error when alerting is not available (elastic#77179) do not log plugin id format warning in dist mode (elastic#77134) [ML] Improving client side error handling (elastic#76743) [Alerting][Connectors] Refactor IBM Resilient: Generic Implementation (phase one) (elastic#74357) [Docs] some basic searchsource api docs (elastic#77038) add cGroupOverrides to the legacy config (elastic#77180) Change saved object bulkUpdate to work across multiple namespaces (elastic#75478) [Security Solution][Resolver] Replace Selectable popover with badges (elastic#76997) Removing ml-state index from archive (elastic#77143) [Security Solution] Add unit tests for histograms (elastic#77081) [Lens] Filters aggregation (elastic#75635) [Enterprise Search] Update WS Overview logic to use new config data (elastic#77122) Cleanup type output before building new types (elastic#77211) [Security Solution] Use safe type in resolver backend (elastic#76969) Use proper lodash syntax (elastic#77105) ... # Conflicts: # x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/components/node_allocation.tsx
Summary
Follow up of #76730.
Add
cGroupOverrides
to the legacy config to avoid config validation failures when using it, and updatekibana-docker
script to use the new config keys