Skip to content

feat: remove future implementation from the pendingdeployment class#679

Open
Sunil-SKS wants to merge 1 commit intoSAP:mainfrom
Sunil-SKS:feat/refactor
Open

feat: remove future implementation from the pendingdeployment class#679
Sunil-SKS wants to merge 1 commit intoSAP:mainfrom
Sunil-SKS:feat/refactor

Conversation

@Sunil-SKS
Copy link
Contributor

The Future implementation has been removed from PendingDeployment to support the migration from Vert.x 4 to Vert.x 5. The PendingDeployment class now returns objects directly, rather than Futures.

@Sunil-SKS Sunil-SKS requested a review from a team as a code owner February 16, 2026 08:27
@Sunil-SKS Sunil-SKS force-pushed the feat/refactor branch 3 times, most recently from 7034ed6 to d55b69b Compare February 16, 2026 14:37
@Sunil-SKS Sunil-SKS changed the title feat: remove future implementation from the class PendingDeployment feat: remove future implementation from the pendingdeployment class Feb 16, 2026
// complete and then undeploy it. pending deployment was completed successfully, undeploy will undeploy
// it, or otherwise will do nothing because a failed deployment results in a successful undeploy
return pendingDeployment.transform(deployResult -> pendingDeployment.undeploy());
return pendingDeployment.undeploy();
Copy link
Contributor

@ikalachy ikalachy Feb 18, 2026

Choose a reason for hiding this comment

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

pendingDeployment.getDeployment().transform(result -> pendingDeployment.undeploy());

pendingDeployment.undeploy() will fail immediately with IllegalStateException if a deployment is still in progress. The old code used transform() to wait for completion; this waiting mechanism was removed, breaking the undeploy logic during partial deployment failures.

Changes -
PendingDeployment
@sonarqubecloud
Copy link

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.

2 participants