You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+24Lines changed: 24 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1099,6 +1099,30 @@ ebWaitOnEnvironmentHealth(
1099
1099
1100
1100
## current master
1101
1101
1102
+
## 1.45
1103
+
### Enhanced ECS and Lambda Deployment Support
1104
+
1105
+
We've improved the `CreateDeployStep` class to better handle ECS and Lambda deployments:
1106
+
1107
+
1. Added a new method `isEcsOrLambdaDeployment()` to detect if the deployment is for ECS or Lambda.
1108
+
2. Modified the `getFileExistsBehavior()` method to skip setting `FileExistsBehavior` for ECS and Lambda deployments.
1109
+
3. These changes ensure that the `fileExistsBehavior` parameter is only set for EC2/On-premises deployments, avoiding potential issues with ECS and Lambda deployments.
1110
+
1111
+
### New Dependencies
1112
+
1113
+
The following new imports have been added to support these changes:
The `isEcsOrLambdaDeployment()` method includes basic error handling to gracefully handle any exceptions that may occur when querying the deployment group information.
1122
+
1123
+
These updates enhance the plugin's compatibility with different AWS CodeDeploy compute platforms while maintaining existing functionality for EC2/On-premises deployments.
1124
+
1125
+
1102
1126
## 1.44
1103
1127
* Fix global configuration naming for JCasC. Please note that this is a breaking change if JCasC is defined. This can be fixed by renaming pluginImpl --> pipelineStepsAWS.
1104
1128
* Fix Elastic Beanstalk client creation bug that ignored provided configurations in the withAWSStep
0 commit comments