[Search] Removing elastic managed connectors misleading content (#213335)

## Summary

Fixing misleading info noted in this GH issue ticket
https://github.com/elastic/search-team/issues/9483 regarding Elastic
managed connectors that are not available in Serverless


Connectors empty state page:

![CleanShot 2025-03-06 at 10 38
45@2x](https://github.com/user-attachments/assets/c26da5f3-ec9a-4ec0-bf6c-a50284556bbd)

Connectors list page (without the Callout banner on top):

![CleanShot 2025-03-06 at 10 41
00@2x](https://github.com/user-attachments/assets/68920905-b2d3-49b8-a2ad-a8500717e129)



### Checklist

Check the PR satisfies following conditions. 

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...
This commit is contained in:
José Luis González 2025-03-06 14:24:11 +01:00 committed by GitHub
parent f195570049
commit c67a239e45
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 10 additions and 57 deletions

View file

@ -35,16 +35,13 @@ export const SelfManagedConnectorsEmptyPrompt: React.FC = () => {
return (
<SearchEmptyPrompt
icon="plugs"
title={i18n.translate('xpack.serverlessSearch.elasticManagedConnectorEmpty.title', {
defaultMessage: 'Elastic managed connectors',
title={i18n.translate('xpack.serverlessSearch.selfManagedConnectorEmpty.title', {
defaultMessage: 'Set up a connector',
})}
description={i18n.translate('xpack.serverlessSearch.selfManagedConnectorEmpty.description', {
defaultMessage:
"To set up and deploy a connector you'll be working between data source, your terminal, and the Kibana UI. The high level process looks like this:",
})}
description={i18n.translate(
'xpack.serverlessSearch.elasticManagedConnectorEmpty.description',
{
defaultMessage:
"We're actively developing Elastic managed connectors, that won't require any self-managed infrastructure. You'll be able to handle all configuration in the UI. This will simplify syncing your data into a serverless Elasticsearch project. This new workflow will have two steps:",
}
)}
body={
<EuiFlexGroup
alignItems="stretch"
@ -179,7 +176,7 @@ export const SelfManagedConnectorsEmptyPrompt: React.FC = () => {
<EuiIcon size="m" type="sortRight" />
</EuiFlexItem>
<EuiFlexItem>
<EuiIcon color="primary" size="l" type="logoElastic" />
<EuiIcon color="primary" size="l" type="logoElasticsearch" />
</EuiFlexItem>
</EuiFlexGroup>
</EuiFlexItem>

View file

@ -7,17 +7,15 @@
import {
EuiButton,
EuiCallOut,
EuiFlexGroup,
EuiFlexItem,
EuiLink,
EuiPageTemplate,
EuiSpacer,
EuiText,
} from '@elastic/eui';
import { i18n } from '@kbn/i18n';
import { FormattedMessage } from '@kbn/i18n-react';
import React, { useMemo, useState } from 'react';
import React, { useMemo } from 'react';
import { GithubLink } from '@kbn/search-api-panels';
import { SelfManagedConnectorsEmptyPrompt } from './connectors/self_managed_connectors_empty_prompt';
@ -29,9 +27,6 @@ import { useKibanaServices } from '../hooks/use_kibana';
import { ConnectorsTable } from './connectors/connectors_table';
import { ConnectorPrivilegesCallout } from './connectors/connector_config/connector_privileges_callout';
import { useAssetBasePath } from '../hooks/use_asset_base_path';
import { BASE_CONNECTORS_PATH, ELASTIC_MANAGED_CONNECTOR_PATH } from '../constants';
const CALLOUT_KEY = 'search.connectors.ElasticManaged.ComingSoon.feedbackCallout';
export const ConnectorsOverview = () => {
const { data, isLoading: connectorsLoading } = useConnectors();
@ -42,14 +37,7 @@ export const ConnectorsOverview = () => {
[consolePlugin]
);
const canManageConnectors = !data || data.canManageConnectors;
const {
application: { navigateToUrl },
} = useKibanaServices();
const [showCallOut, setShowCallOut] = useState(sessionStorage.getItem(CALLOUT_KEY) !== 'hidden');
const onDismiss = () => {
setShowCallOut(false);
sessionStorage.setItem(CALLOUT_KEY, 'hidden');
};
const assetBasePath = useAssetBasePath();
return (
@ -116,39 +104,7 @@ export const ConnectorsOverview = () => {
<EuiPageTemplate.Section restrictWidth color="subdued">
<ConnectorPrivilegesCallout />
{connectorsLoading || (data?.connectors || []).length > 0 ? (
<>
{showCallOut && (
<>
<EuiCallOut
size="m"
title="Coming soon Elastic managed connectors."
iconType="pin"
onDismiss={onDismiss}
>
<p>
{i18n.translate(
'xpack.serverlessSearch.connectorsOverview.calloutDescription',
{
defaultMessage:
"We're actively developing Elastic managed connectors, that won't require any self-managed infrastructure. You'll be able to handle all configuration in the UI. This will simplify syncing your data into a serverless Elasticsearch project.",
}
)}
</p>
<EuiButton
data-test-subj="serverlessSearchConnectorsOverviewLinkButtonButton"
color="primary"
onClick={() =>
navigateToUrl(`${BASE_CONNECTORS_PATH}/${ELASTIC_MANAGED_CONNECTOR_PATH}`)
}
>
{LEARN_MORE_LABEL}
</EuiButton>
</EuiCallOut>
<EuiSpacer size="m" />
</>
)}
<ConnectorsTable />
</>
<ConnectorsTable />
) : (
<SelfManagedConnectorsEmptyPrompt />
)}