elastic/kibana

[Fleet]: Incorrect error message is displayed at the top of the policy editor while adding AWS integration when no Fleet Server exists.

Open

#180992 opened on Apr 17, 2024

View on GitHub
 (8 comments) (0 reactions) (0 assignees)TypeScript (19,065 stars) (8,021 forks)batch import
Team:Fleetbuggood first issueimpact:low

Description

Kibana Build details:

VERSION: 8.14.0-SNAPSHOT
BUILD: 73413
COMMIT: cba0e7f3f18ab7fd48ee30b0385a599d211eac7d

Host OS: All

Preconditions:

  1. 8.14.0-SNAPSHOT Kibana cloud environment should be available.

Steps to reproduce:

  1. Navigate to Fleet>Agents tab and observe no hosted fleet server is available.
  2. Navigate to Integrations and add AWS integration.
  3. Observe error message: This integration contains policy secrets(opens in a new tab or window), but you have a Fleet Server running on a version earlier than 8.10.0. Please upgrade your Fleet Server to enable policy secrets for all integrations.

Expected Result: Correct error message should be displayed under policy editor while adding AWS integration when no Fleet Server exists. This integration contains policy secrets(opens in a new tab or window), but Fleet Server is not available. Please install Fleet Server to enable policy secrets for all integrations.

Screen Recording:

https://github.com/elastic/kibana/assets/77374876/38608d3a-ce4c-4cb0-b09c-518531775b88

Feature: https://github.com/elastic/kibana/pull/178045

Contributor guide

Tech stack
typescriptreactnodejs
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
ReactTypeScriptKibana Fleet
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
The error message is displayed in the Fleet plugin's policy editor when adding AWS integration. The current message incorrectly assumes a Fleet Server exists but is on an older version. The fix involves modifying the condition that controls this message to also handle the case where no Fleet Server exists. Look at the linked PR #178045 for context. The relevant code is likely in x pack/plugins/fleet/public or similar. Check for where the version check is performed and add a separate check for absence of Fleet Server. Update the string to show the appropriate message based on the actual state.