Skip to content

Comments

Replace BakeStatusPending with BakeStatusDeploying#35

Merged
LittleChimera merged 1 commit intomainfrom
replace-pending-with-deploying-status
Dec 26, 2025
Merged

Replace BakeStatusPending with BakeStatusDeploying#35
LittleChimera merged 1 commit intomainfrom
replace-pending-with-deploying-status

Conversation

@LittleChimera
Copy link
Contributor

@LittleChimera LittleChimera commented Dec 26, 2025

  • Rename BakeStatusPending constant to BakeStatusDeploying in API types
  • Update all references from Pending to Deploying in controller logic
  • Update test assertions and descriptions to use Deploying status
  • Update status messages and event names to reflect Deploying status

Note

Standardizes bake pre-start phase terminology.

  • API: Replace BakeStatusPending with BakeStatusDeploying in rollout_types.go.
  • Controller: Treat Deploying equivalently to previous Pending in bake-time evaluation, blocking, cancellation, and transitions to InProgress; update status summaries and initial bake state to Deploying; change event BakeTimePending to BakeTimeDeploying.
  • Tests: Update assertions and descriptions to expect Deploying instead of Pending across bake gating, release candidate population, cancellation, timeouts, and failure paths.

Written by Cursor Bugbot for commit 88c8bb5. This will update automatically on new commits. Configure here.

- Rename BakeStatusPending constant to BakeStatusDeploying in API types
- Update all references from Pending to Deploying in controller logic
- Update test assertions and descriptions to use Deploying status
- Update status messages and event names to reflect Deploying status
@LittleChimera LittleChimera merged commit 731200d into main Dec 26, 2025
4 of 8 checks passed
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.


const (
BakeStatusPending = "Pending"
BakeStatusDeploying = "Deploying"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Breaking change: existing "Pending" status resources become orphaned

The constant BakeStatusPending was renamed to BakeStatusDeploying but the string value also changed from "Pending" to "Deploying". Existing Rollout resources in Kubernetes with BakeStatus: "Pending" stored in etcd will no longer be recognized by the controller's switch statements that now check for "Deploying". This causes handleBakeTime to be skipped for those resources, potentially leaving them stuck in an unrecognized state without proper bake time handling. To safely rename while maintaining backward compatibility, the value should remain "Pending" or migration logic is needed.

Additional Locations (2)

Fix in Cursor Fix in Web

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.

1 participant