Evaluate QA GitHub Actions for Cloudbeat handover

[uri-weisman]

Summary

Review the Cloudbeat GitHub Actions that currently support the QA process and map which actions are still needed by the contextual team as part of the handover.

A specific decision point is whether the existing environment-creation flow should remain in the GitHub Action workflow, or whether it should be replaced with a new flow built on currently supported tooling such as the oblt CLI.

Scope

• Inventory the Cloudbeat QA-related GitHub Actions and the steps they perform today.
• Identify which actions should be kept, removed, or replaced.
• If replacement is preferred, outline the recommended approach and supporting tooling.

Acceptance Criteria

• A documented mapping exists for the Cloudbeat QA GitHub Action steps in use today.
• Each action/step is categorized as keep, remove, or replace for the contextual team.
• There is a recommendation on whether to continue using the current environment-creation flow.
• If a new approach is preferred, the issue captures the proposed replacement path and next implementation steps.

[gurevichdmitry]

Workflow overview

#	Workflow file	Display name	Triggers	Primary purpose	Calls other workflows	Handover category
1	test-environment.yml	Create Environment	manual, reusable	Provision an ESS or Serverless stack; install CDR and/or CIS integrations on real cloud/VM/K8s resources (Elastic Agent–based and/or agentless). Optionally run Python integration sanity tests and Kibana UI tests.	—	TBD
2	test-e2e-flow.yml	Test E2E Flow	reusable	Parameterized nightly E2E flow: provision an environment with real integration data, run integration and UI sanity tests, then destroy it. Used for both ESS and Serverless.	test-environment.yml, destroy-environment.yml	TBD
3	test-runner.yml	Test Runner	manual, schedule	Nightly orchestrator on main: defines cron schedule, run order, and inputs (ESS first, then Serverless).	test-e2e-flow.yml (×2 jobs)	TBD
4	cdr-infra.yml	Create Environment with Cloud Logs (CDR)	manual	Manual dispatch focused on CDR (cloud logs): provision ESS or Serverless and install CDR integrations with real ingestion on agent-based hosts. Optionally add CIS when cis-infra is enabled.	test-environment.yml	TBD
5	install-integrations.yml	Install Integrations	manual	Attach CDR and/or CIS integrations to an existing stack (no new ELK deploy). Agent-based only (agentless: false).	test-environment.yml	TBD
6	upgrade-environment.yml	Test Upgrade Environment	manual	Deploy a base stack with CIS on real agent-based infrastructure → upgrade ELK stack and agents → run post-upgrade integration sanity and UI tests.	test-environment.yml	TBD
7	create-env-ea.yml	Create EA Environment	manual	EA / demo path: deploy ELK only and populate with generated demo data (no CDR/CIS on real or agentless collectors). See Table 2.	—	TBD
8	destroy-environment.yml	Destroy Environment	manual, reusable	Tear down an environment created by Create Environment (manual dispatch or reusable call).	—	TBD
9	destroy-expired-environment.yml	Destroy Expired Environment	schedule	Daily cleanup: find deployments past expiration (S3 config) and destroy each one.	destroy-environment.yml	TBD