Add support for essentials and ease tiers in Scout

[MadameSheema]

Summary

Adds support for the essentials and ease severless tiers to the Scout testing framework, enabling local server startup with the Security Essentials and Security EASE tier configuration.

Testing

• Verified that node scripts/scout.js start-server --serverless=security-essentials successfully starts the environment
• Verified that node scripts/scout.js start-server --serverless=security-ease successfully starts the environment

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[fake-haris]

just to make sure: serverless arg should be security. Not EASE or essentials?

[MadameSheema]

Right, serverless arg should be security, EASE and essentials refers to the tier used in the security project.

[dmlemeshko]

LGTM

@MadameSheema I think it would be better to backport PR to "all-open" to avoid merge conflicts in the future even though we don't run svl tests in those branches.

With this PR tests won't be run for tiers, you need to make changes in

kibana/.buildkite/scripts/steps/test/scout_configs.sh

Lines 62 to 74 in 4fc8027

	# Define run modes based on group
	declare -A RUN_MODES
	RUN_MODES["platform"]="--stateful --serverless=es --serverless=oblt --serverless=security"
	RUN_MODES["observability"]="--stateful --serverless=oblt --serverless=oblt-logs-essentials"
	RUN_MODES["search"]="--stateful --serverless=es"
	RUN_MODES["security"]="--stateful --serverless=security"
	# Define serverless-only run modes based on group
	declare -A RUN_MODES_SERVERLESS_ONLY
	RUN_MODES_SERVERLESS_ONLY["platform"]="--serverless=es --serverless=oblt --serverless=security"
	RUN_MODES_SERVERLESS_ONLY["observability"]="--serverless=oblt --serverless=oblt-logs-essentials"
	RUN_MODES_SERVERLESS_ONLY["search"]="--serverless=es"
	RUN_MODES_SERVERLESS_ONLY["security"]="--serverless=security"

I'm not sure if we need to run all the platform tests for each tier, let me know you thoughts

[MadameSheema]

With this PR tests won't be run for tiers, you need to make changes in

Thank you for pointing this out! I'll make the changes 😊

I'm not sure if we need to run all the platform tests for each tier, let me know you thoughts

I’m not sure because I don’t know what the platform tests cover. Could you please share the link with me?

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 2b84aaa

Failed CI Steps

• FTR Configs #52
• FTR Configs #77

Test Failures

• [job] [logs] FTR Configs #77 / Console App CCS Perform CCS Search in Console it should be able to access remote data

Metrics [docs]

✅ unchanged

History

• 💚 Build #366654 succeeded ddf2ecc
• 💚 Build #366520 succeeded e55c4da
• 💔 Build #366508 failed 36a547c
• 💔 Build #366472 failed d8622b1

cc @MadameSheema

[delanni]

scout_configs.sh 👍

Side question:
@elastic/appex-qa - do you think the tools/scripts around scout are located close enough, so we could share or hand over ownership of these scripts? You probably know more about it, so your approval might be more relevant

[kibanamachine]

Starting backport for target branches: 8.19, 9.1, 9.2

https://github.com/elastic/kibana/actions/runs/19853977541

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	8.19	Backport failed because of merge conflicts
❌	9.1	Backport failed because of merge conflicts
❌	9.2	Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 244553

Questions ?

Please refer to the Backport tool documentation