Skip to content

feat: update deploymentpipelineref to an object#22

Open
yashodgayashan wants to merge 1 commit intomainfrom
deploymentpipelineref
Open

feat: update deploymentpipelineref to an object#22
yashodgayashan wants to merge 1 commit intomainfrom
deploymentpipelineref

Conversation

@yashodgayashan
Copy link
Contributor

@yashodgayashan yashodgayashan commented Mar 5, 2026

Purpose

Update deploymentpipelineref to an object to support new CR

Approach

Summarize the solution and implementation details.

Related Issues

openchoreo/openchoreo#2264

Checklist

  • Tests added or updated (unit, integration, etc.)
  • Samples updated (if applicable)

Remarks

Add any additional context, known issues, or TODOs related to this PR.

Summary by CodeRabbit

  • Chores
    • Updated deployment pipeline reference format in project configuration from scalar string to structured object format. Existing configuration files may require updates to reflect the new reference structure.

Signed-off-by: yashodgayashan <yashodgayashan@gmail.com>
@coderabbitai
Copy link

coderabbitai bot commented Mar 5, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5bec4da7-8e03-4d62-967c-736409d7de1f

📥 Commits

Reviewing files that changed from the base of the PR and between 4cf6ff6 and 36d01d4.

📒 Files selected for processing (1)
  • namespaces/default/projects/doclet/project.yaml

📝 Walkthrough

Walkthrough

The spec.deploymentPipelineRef field in the project configuration was converted from a scalar string value to an object structure with a name property. This represents a type change from string to mapping in the configuration schema.

Changes

Cohort / File(s) Summary
Configuration Schema Update
namespaces/default/projects/doclet/project.yaml
Changed spec.deploymentPipelineRef from scalar string (standard) to structured object ({ name: standard }).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Possibly related PRs

Suggested reviewers

  • LakshanSS

Poem

🐰 A reference once simple, now dressed in a gown,
From string to an object, the schema flows down,
The name finds its place in structured delight,
Configuration dancing—a marshalling rite! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: updating deploymentPipelineRef from a scalar string to an object structure, which aligns with the file modifications shown in the raw summary.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch deploymentpipelineref

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Project CRD spec doesn't support using ClusterDeploymentPipeline entities

1 participant