Convert claudio Task to StepAction

[jangel97]

Summary

• Replace the monolithic Tekton Task with a composable StepAction
• The consuming Task is now responsible for defining volumes and secrets
• Drops envFrom, workspaces, and env-secrets — these are concerns of the consuming Task
• Documentation moved into tekton.dev/description annotation with prerequisites and usage example

Why

As a StepAction, claudio becomes a reusable building block that can be composed into any Task via ref. Each team wires up their own secrets/volumes in their Task, keeping claudio generic.

Test plan

• Apply the StepAction to a cluster
• Reference it from a Task via ref and verify it runs with a prompt
• Verify GCP credentials are mounted correctly via the parameterized volume

Summary by CodeRabbit

• Refactor
  • Updated CI/CD integration configuration with modernized credential handling and streamlined parameter interface to reduce complexity.
  • Simplified execution setup and resource mounting configuration for improved maintainability.

[coderabbitai]

📝 Walkthrough

Walkthrough

The claudio Tekton definition migrates from a reusable Task (apiVersion: tekton.dev/v1) to a StepAction (apiVersion: tekton.dev/v1beta1). Parameters are updated to expose image, gcp-volume, and output-volume directly. Execution is simplified to set environment variables directly and mount credentials and output volumes, removing the previous kubectl-based secret-expansion logic.

Changes

StepAction Conversion

Layer / File(s)	Summary
StepAction definition and parameter surface integrations/tekton/claudio.yml	Kind changes from Task to StepAction with apiVersion v1beta1. Parameters image, gcp-volume, and output-volume are added; gcp-credentials and env-secrets are removed. Workspace declarations are removed.
Execution specification with volume mounts integrations/tekton/claudio.yml	Execution spec sets GOOGLE_APPLICATION_CREDENTIALS and other env variables directly, uses $(params.image) for the container image, mounts gcp-volume at /var/run/secrets/gcp and output-volume at /home/claudio/output, and invokes entrypoint.sh -p $(params.prompt) with $(params.extra-args).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~35 minutes

Possibly related PRs

• aipcc-cicd/claudio#145: Predecessor PR that established the original Task-based pattern with kubectl-driven secret expansion, which this PR refactors into a StepAction.

Suggested reviewers

• adrianriobo

Poem

🐰 A Task becomes a Step so grand,
With volumes mounted, env at hand,
No kubectl spells, just mounts so clean,
The claudio action, sleek and keen! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely describes the main change: converting the claudio Tekton definition from a Task to a StepAction.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch tekton-stepaction

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}