-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
codedeploy: zonal configuration for the EC2/on-premises deploy configuration #30430
codedeploy: zonal configuration for the EC2/on-premises deploy configuration #30430
Comments
thanks @badmintoncryer for submitting the PR. |
|
1 similar comment
|
…30429) ### Issue # (if applicable) Closes #30430 ### Reason for this change `ServerDeploymentConfig` does not support for configuring the [zonal configuration](https://docs.aws.amazon.com/codedeploy/latest/userguide/deployment-configurations-create.html#zonal-config). ### Description of changes - define `ZonalConfig` interface - define `MinimumHealthyHostsPerZone` class - add `zonalConfig` property to the `BaseDeploymentConfigProps` ### Description of how you validated changes Add both unit and integ tests ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Comments on closed issues and PRs are hard for our team to see. If you need help, please open a new issue that references this one. |
Describe the feature
Configure zonal configuration for the EC2/on-premises deploy configuration.
Use Case
ServerDeploymentConfig
class does not support for configuring zonal configuration.Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
2.141.0
Environment details (OS name and version, etc.)
irrelevant
The text was updated successfully, but these errors were encountered: