Epic Goal

Currently, StepActions in Tekton are in beta, and needs to be promoted to GA. It is currently being tracked in an upstream issue here https://github.com/tektoncd/pipeline/issues/8485

Why is this important?

• StepActions allow for extended modularity through template-able steps. Currently, steps cannot be inherited from a template and used, this forces users to redefine steps over and over again in Tasks and TaskRuns.

• With the addition of StepActions, the reusability of steps will be promoted while allowing them to create Pipelines faster.

Scenarios

1. Task 1 and 2 have the same complex step which they use but the complex step needs to be defined in each of the Tasks because a templated version of the step doesn't exist. In this scenario, having a StepAction helps.

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Completion of https://github.com/tektoncd/pipeline/issues/8485 which contains the following issues.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment