[ML] Removing global isServerless flag#166651
Conversation
…elastic/kibana into removing-global-isServerless-flag
…elastic/kibana into removing-global-isServerless-flag
|
Pinging @elastic/ml-ui (:ml) |
| </EuiButton> | ||
| </EuiToolTip> | ||
| {isServerless || hideFrozenDataTierChoice ? null : ( | ||
| {showFrozenDataTierChoice && showFrozenDataTierChoiceProp ? ( |
There was a problem hiding this comment.
What happens when showFrozenDataTierChoice from useDatePickerContext is undefined but showFrozenDataTierChoiceProp is explicity set to true? If both have to be true, might be good to document that in the FullTimeRangeSelectorProps.
There was a problem hiding this comment.
This is a mistake introduced by me switching from "hide" to "show" in the variable names.
Looking at this again though, I don't think the prop is needed at all anymore. Everywhere this component is used it's wrapped in the data picker context.
|
Tested latest changes and LGTM 🎉 |
| useTimefilter({ timeRangeSelector: false, autoRefreshSelector: true }); | ||
|
|
||
| const isServerless = useIsServerless(); | ||
| const { showNodeInfo } = useEnabledFeatures(); |
There was a problem hiding this comment.
Fixed in 14e1f50
I had incorrectly moved the model management route registration behind a check for dfa and nlp features, thinking the routes are for trained model management only.
However these routes are for AD models too.
peteharverson
left a comment
There was a problem hiding this comment.
Latest changes LGTM
…elastic/kibana into removing-global-isServerless-flag
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
Canvas Sharable Runtime
Page load bundle
History
To update your PR or re-run it, just comment with: |

Removed
isServerlessflag which lived in our global context and had to be passed about to the various components which create their own version of the context usinggetMlGlobalServicesThis PR adds a new context which contains flags for all of the features which can be toggled when in serverless mode.
Flags added:
The enabled features flags are now read from the config file client side, rather than using capabilities.
Additional changes: