From db57ca5ff568095b930f562ccc812e024aa70bdf Mon Sep 17 00:00:00 2001 From: Michael Olorunnisola Date: Thu, 2 May 2024 15:18:05 -0400 Subject: [PATCH] [Security Solution] - Rename esql setting (#182432) ## Summary Follow up to this PR: https://github.com/elastic/kibana/pull/181616 Renaming `discover:enableEsql` to `enableESQL` according to this change: https://github.com/elastic/kibana/pull/182074 --- .../public/common/hooks/esql/use_esql_availability.ts | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/x-pack/plugins/security_solution/public/common/hooks/esql/use_esql_availability.ts b/x-pack/plugins/security_solution/public/common/hooks/esql/use_esql_availability.ts index a9df259addf49cd..41fc7084b32bfdd 100644 --- a/x-pack/plugins/security_solution/public/common/hooks/esql/use_esql_availability.ts +++ b/x-pack/plugins/security_solution/public/common/hooks/esql/use_esql_availability.ts @@ -6,12 +6,18 @@ */ import { useMemo } from 'react'; +import { ENABLE_ESQL } from '@kbn/esql-utils'; import { useKibana } from '../../lib/kibana'; import { useIsExperimentalFeatureEnabled } from '../use_experimental_features'; +/** + * This hook combines the checks for esql availability within the security solution + * If the advanced setting is disabled, ESQL will not be accessible in the UI for any new timeline or new rule creation workflows + * The feature flags are still available to provide users an escape hatch in case of any esql related performance issues + */ export const useEsqlAvailability = () => { const { uiSettings } = useKibana().services; - const isEsqlAdvancedSettingEnabled = uiSettings?.get('discover:enableESQL'); + const isEsqlAdvancedSettingEnabled = uiSettings?.get(ENABLE_ESQL); const isEsqlRuleTypeEnabled = !useIsExperimentalFeatureEnabled('esqlRulesDisabled') && isEsqlAdvancedSettingEnabled; const isESQLTabInTimelineEnabled =