Remove transitional status configuration from deployment settings and update deployment logic - #3145
Conversation
… related code references. Update deployment logic to assume transitional status until gateway acknowledgment is received. Adjust polling behavior to handle timeout for transitional deployments, ensuring they are marked as FAILED if not acknowledged in time.
|
Warning Review limit reached
Next review available in: 2 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
📝 WalkthroughWalkthroughThe deployment status configuration flag is removed. Backend operations always start in transitional states. Desired terminal statuses are persisted and reported. Workspace polling now resolves terminal states and marks unresolved operations as failed after 80 seconds. ChangesDeployment status flow
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant DeploymentService
participant DeploymentRepository
participant GatewayDeployContext
participant GatewayDeployEnvCard
DeploymentService->>DeploymentRepository: Store transitional status and desired status
GatewayDeployContext->>DeploymentRepository: Poll deployment status
DeploymentRepository-->>GatewayDeployContext: Return current and desired status
GatewayDeployContext-->>GatewayDeployEnvCard: Expose effective status
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@portals/ai-workspace/src/contexts/GatewayDeployContext.tsx`:
- Around line 437-442: Update the rejected-result handling in the deployment
polling flow around fetchSingleDeploymentStatus so transient status-read
failures remain active and are retried until expiresAt. Do not add rejected
entries to resolved or timedOut during the polling window; only mark them failed
after the deadline when the server still reports a transitional status.
- Around line 72-82: Remove the hard-coded TRANSITIONAL_POLL_TIMEOUT_MS limit
from GatewayDeployContext and obtain the effective deployment timeout or
operation deadline from platform-api. Use that server-provided value to bound
transitional-status polling, preserving accurate behavior when timeout settings
are disabled or configured differently.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 0532bbc0-7d9a-4bab-b2a7-f7924bbddd21
📒 Files selected for processing (11)
kubernetes/helm/platform-api-helm-chart/templates/configmap.yamlkubernetes/helm/platform-api-helm-chart/values.yamlplatform-api/config/config-template.tomlplatform-api/config/config.goplatform-api/internal/service/deployment.goplatform-api/internal/service/llm_deployment.goplatform-api/internal/service/mcp_deployment.goplatform-api/plugins/eventgateway/service/webbroker_api_deployment.goplatform-api/plugins/eventgateway/service/websub_api_deployment.goportals/ai-workspace/src/Components/GatewayDeploy/GatewayDeployEnvCard.tsxportals/ai-workspace/src/contexts/GatewayDeployContext.tsx
💤 Files with no reviewable changes (3)
- kubernetes/helm/platform-api-helm-chart/templates/configmap.yaml
- kubernetes/helm/platform-api-helm-chart/values.yaml
- platform-api/config/config-template.toml
…g and undeploying. Adjust polling interval for deployments and enhance error handling during status reads to allow for transient failures.
…e related checks across services to enhance deployment status handling.
…ath for certificate verification.
Remove transitional status configuration from deployment settings and related code references. Update deployment logic to assume transitional status until gateway acknowledgment is received. Adjust polling behavior to handle timeout for transitional deployments, ensuring they are marked as FAILED if not acknowledged in time.