fix: skip creating deployments if current and target versions match #85
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.
It appears AWS CodeDeploy will reject deployments where the CurrentVersion and TargetVersion match (edit: if the deployment config is anything other than all-at-once, e.g. canary or linear rollout). We avoid creating such a failing deployment by ignoring cases where the current and target versions already match in the deploy script.
Fixes #82, where there's a lot more detail on the motivation here.