Repository navigation
fix: detect resource deletion in duplicate deployment filter - #4328
Open
omkasera972-ai wants to merge 1 commit into
Open
omkasera972-ai wants to merge 1 commit into
omkasera972-ai wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Code <noreply@anthropic.com>
This branch has not been deployed
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.
Description
This pull request fixes a logic bug in the duplicate deployment filter (
deploymentsDiffermethod insideDeployCmd).Previously, when checking if a new deployment differed from an existing saved deployment, the code only iterated over the resources present in the new deployment. If a user deleted a non-generated resource (such as a BPMN XML file) while keeping the remaining resources identical, the duplicate detector failed to notice the deletion and incorrectly returned
false. This caused the engine to skip creating the new deployment and retain the old state.Changes
deploymentsDifferinDeployCmd.javato iterate throughsavedResourcesand check if any non-generated resource was removed (i.e., exists in saved deployment but missing in the new deployment).true, triggering a new deployment.Checklist