WIP: Add a helper to generate yaml to test scripts - #980
Conversation
|
Important Review skippedIgnore keyword(s) in the title. ⛔ Ignored keywords (3)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: feichashao The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@feichashao: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #980 +/- ##
==========================================
+ Coverage 54.54% 56.27% +1.72%
==========================================
Files 82 83 +1
Lines 6308 6648 +340
==========================================
+ Hits 3441 3741 +300
- Misses 2417 2439 +22
- Partials 450 468 +18
🚀 New features to boost your workflow:
|
What type of PR is this?
What this PR does / Why we need it?
Assisted by Claude.
This is a helper function to generate yaml files from a managed scripts (with metadata). This is for local test on a staging cluster manually when developing a managed script.
WIP: I haven't reviewed/validate this command yet. Raising it for discussion. If we want to go with it, I will review it closely and validate it in a staging cluster.
Test steps provided by Claude:
Step 1 — Create mock metadata and script files
metadata.yaml
script.sh
Step 2 — Run the render command
Step 3 — Generated YAML
The command produces a multi-document YAML file containing all the Kubernetes objects needed to run the test script. This matches what the backplane-api's server-side dry-run generates:
Step 4 — Apply on a staging cluster
Which Jira/Github issue(s) does this PR fix?
Special notes for your reviewer
Unit Test Coverage
Guidelines
Test coverage checks
Pre-checks (if applicable)
/label tide/merge-method-squash