Skip to content

fix: detect resource deletion in app engine duplicate deployment filter - #4329

Open
omkasera972-ai wants to merge 2 commits into
flowable:mainfrom
omkasera972-ai:fix/deploy-resource-deletion-app-engine
Open

omkasera972-ai wants to merge 2 commits into
flowable:mainfrom
omkasera972-ai:fix/deploy-resource-deletion-app-engine

Conversation

@omkasera972-ai

Copy link
Copy Markdown

Description

This pull request fixes a logic bug in the app engine duplicate deployment filter (deploymentsDiffer method inside DeployCmd in flowable-app-engine).

Previously, when checking if a new app deployment differed from an existing saved deployment, the code only checked resources present in the new deployment. If a user deleted a non-generated resource while keeping the remaining resources identical, the duplicate filter failed to detect the deletion and returned false. This caused the app engine to skip creating the new deployment.

Changes

  • Updated deploymentsDiffer in modules/flowable-app-engine/src/main/java/org/flowable/app/engine/impl/cmd/DeployCmd.java to check if any non-generated resource in savedResources was removed in the new deployment.
  • Returns true when a resource deletion is detected so that a new deployment is properly created.

Checklist

  • Unit tests: NA (Logic fix on duplicate filter check)
  • Documentation: NA

🤖 Generated with Claude Code

This branch has not been deployed

No deployments
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