feat(openchoreo): show suspended state in the deployment pipeline

[isala404]

What

A component whose workload is scaled to zero showed as "Active" in the deployment pipeline, which is misleading. This adds a distinct "Suspended" state so it reads correctly.

How

Core already reports the suspended state on the ReleaseBinding's ResourcesReady condition (reason ReadyWithSuspendedResources), but the backend transformer only looked at the Ready condition, which stays Ready for a scaled-to-zero workload. The transformer now also checks ResourcesReady on a Ready binding and surfaces that reason, and the frontend maps it to a new suspended badge variant labelled "Suspended".

• release-binding.ts reads the ResourcesReady reason on a Ready binding.
• useEnvironmentStatusVariant.ts maps ReadyWithSuspendedResources to a suspended variant.
• StatusBadge.tsx adds the suspended variant (amber, matching the existing suspended styling in the resource tree).

No core change is needed. The state is already aggregated onto the ReleaseBinding.

Testing

Unit tests added for the transformer, the status hook, and the badge. The data path was checked against a live cluster: a scaled-to-zero component's ReleaseBinding carries ResourcesReady=ReadyWithSuspendedResources, which is what the backend now reads. Affected tests, lint, and prettier pass, and the touched files are type-clean.

Part of #3104

[coderabbitai]

Warning

Review limit reached

@isala404, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 28 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4bc95d45-7232-4d60-b346-fb4de50d2f29

📥 Commits

Reviewing files that changed from the base of the PR and between 383e7f6 and 55a778e.

📒 Files selected for processing (7)

• .changeset/suspended-pipeline-status.md
• packages/design-system/src/components/StatusBadge/StatusBadge.test.tsx
• packages/design-system/src/components/StatusBadge/StatusBadge.tsx
• plugins/openchoreo-backend/src/services/transformers/release-binding.test.ts
• plugins/openchoreo-backend/src/services/transformers/release-binding.ts
• plugins/openchoreo/src/components/Environments/hooks/useEnvironmentStatusVariant.test.ts
• plugins/openchoreo/src/components/Environments/hooks/useEnvironmentStatusVariant.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!