[OGUI-1745] ECS GUI Migration to new api/deploy endpoint - #3001
Merged
graduta merged 40 commits intoAug 19, 2025
Conversation
…OGUI-1675/front-end-migration-to-deploy-endpoint
There was a problem hiding this comment.
Pull Request Overview
This PR migrates the ECS GUI front-end to use a new api/deploy endpoint that relies on Kafka events for live updates instead of the previous polling-based approach. The changes implement a more event-driven architecture for environment deployment and management.
- Replaces the old environment creation workflow with a new async deployment endpoint
- Introduces custom ECS GUI attributes (
isDeploying,deploymentError) for better deployment state tracking - Redirects users to environment details page after deployment instead of the environments overview
Reviewed Changes
Copilot reviewed 42 out of 43 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
Control/public/environment/Environment.js |
Updates environment creation logic to use new /api/deploy endpoint and redirect to environment details |
Control/public/pages/Environments/Environments.page.js |
New environments page component with failed deployment acknowledgment functionality |
Control/lib/services/Environment.service.js |
Updates environment service to handle deploying environments and deployment errors |
Control/lib/controllers/Deployment.controller.js |
New deployment controller with acknowledgment endpoint |
Control/lib/services/environment/EnvironmentCache.service.js |
Enhanced cache service with deployment state tracking and event handling |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
graduta
deleted the
feature/COG/OGUI-1675/front-end-migration-to-deploy-endpoint
branch
August 19, 2025 13:36
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have JIRA issue created
PR which:
api/deployendpoint which now relies on kafka events for live updatesisDeployingwhich is kept while the environment automatically transitions through ECS states until it reachesCONFIGUREDwith no other transition ongoingdeploymentErrorwhich is to be used to display environments that failed to deploy and await user's acknowledgement.deployendpoint usesnewEnvironmentAsyncwithout an error in return but with errors followed as events via Kafkadeployment