-
Notifications
You must be signed in to change notification settings - Fork 48
Open
Labels
Team:Core analysiscloudbeatenhancementNew feature or requestNew feature or requestgithub_actionsPull requests that update GitHub Actions codePull requests that update GitHub Actions code
Description
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.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Team:Core analysiscloudbeatenhancementNew feature or requestNew feature or requestgithub_actionsPull requests that update GitHub Actions codePull requests that update GitHub Actions code
Type
Fields
Give feedbackNo fields configured for issues without a type.