harmonise links to documentation in CSP integration for all cloud providers · elastic/kibana#192971

(4 comments) (0 reactions) (1 assignee)TypeScript (19,065 stars) (8,021 forks)batch import

Feature:Cloud-SecurityTeam:Cloud Securitygood first issue

Description

Motivation

In the Setup Access step of CSPM integration, we have the "Read the documentation for more details" link after the setup method selector (CloudFormation/ARM Template/Google Shell vs Manual). These links follow different logic for each cloud provider while the logic should be the same:

For Manual setup method the link should be rendered after the "Preferred manual method" selector but before the input for package variables (as for AWS Manual right now)
For automated setup methods the link should lead to the Elastic docs, to the relevant part, eg. for Azure ARM https://www.elastic.co/guide/en/security/current/cspm-get-started-azure.html#cspm-set-up-ARM
For manual setup methods the link should lead to the Elastic docs, to the relevant part, eg. for AWS Direct Keys https://www.elastic.co/guide/en/security/current/cspm-get-started.html#cspm-use-keys-directly

related Slack thread

Definition of done

The link "Read the documentation for more details" logic updated accordingly

Out of scope

Related tasks/epics

Team tag

@elastic/kibana-cloud-security-posture -->

Contributor guide

Tech stack: typescriptreactnodejs
Domain: frontenddocumentationsecurity
Issue type: refactor
Difficulty: 2
Estimated time: 1-3 hours
Activity status: active
Clarity: mostly clear
Prerequisites: Familiarity with Kibana CSP integrationUnderstanding of cloud provider setup methods
Newbie friendliness: 70
Research direction: The issue is to unify the logic for rendering the 'Read the documentation for more details' link across cloud providers in CSPM integration. The current implementation has different behavior per provider. The solution should modify the relevant UI components in the Kibana security solution. Check the current implementation in files related to CSPM setup steps, likely under `x pack/plugins/security solution/...`. The Slack thread reference may contain additional details. The assignee's existing work or comments should be reviewed to avoid duplication.