update_deployment_group
async
¶
update_deployment_group(
application_name: ApplicationName,
current_deployment_group_name: DeploymentGroupName,
*,
config_overrides: Optional[AsyncCodeDeployClientConfig] = None,
new_deployment_group_name: Optional[DeploymentGroupName] = None,
deployment_config_name: Optional[DeploymentConfigName] = None,
ec2_tag_filters: Optional[EC2TagFilterList] = None,
on_premises_instance_tag_filters: Optional[TagFilterList] = None,
auto_scaling_groups: Optional[AutoScalingGroupNameList] = None,
service_role_arn: Optional[Role] = None,
trigger_configurations: Optional[TriggerConfigList] = None,
alarm_configuration: Optional[AlarmConfiguration] = None,
auto_rollback_configuration: Optional[AutoRollbackConfiguration] = None,
outdated_instances_strategy: Optional[OutdatedInstancesStrategy] = None,
deployment_style: Optional[DeploymentStyle] = None,
blue_green_deployment_configuration: Optional[
BlueGreenDeploymentConfiguration
] = None,
load_balancer_info: Optional[LoadBalancerInfo] = None,
ec2_tag_set: Optional[EC2TagSet] = None,
ecs_services: Optional[ECSServiceList] = None,
on_premises_tag_set: Optional[OnPremisesTagSet] = None,
termination_hook_enabled: Optional[NullableBoolean] = None,
) -> UpdateDeploymentGroupOutput
Changes information about a deployment group.
Parameters:
-
application_name(ApplicationName) –The application name that corresponds to the deployment group to update.
-
current_deployment_group_name(DeploymentGroupName) –The current name of the deployment group.
-
new_deployment_group_name(Optional[DeploymentGroupName], default:None) –The new name of the deployment group, if you want to change it.
-
deployment_config_name(Optional[DeploymentConfigName], default:None) –The replacement deployment configuration name to use, if you want to change it.
-
ec2_tag_filters(Optional[EC2TagFilterList], default:None) –The replacement set of Amazon EC2 tags on which to filter, if you want to change them. To keep the existing tags, enter their names. To remove tags, do not enter any tag names.
-
on_premises_instance_tag_filters(Optional[TagFilterList], default:None) –The replacement set of on-premises instance tags on which to filter, if you want to change them. To keep the existing tags, enter their names. To remove tags, do not enter any tag names.
-
auto_scaling_groups(Optional[AutoScalingGroupNameList], default:None) –The replacement list of Auto Scaling groups to be included in the deployment group, if you want to change them.
-
To keep the Auto Scaling groups, enter their names or do not specify this parameter.
-
To remove Auto Scaling groups, specify a non-null empty list of Auto Scaling group names to detach all CodeDeploy-managed Auto Scaling lifecycle hooks. For examples, see Amazon EC2 instances in an Amazon EC2 Auto Scaling group fail to launch and receive the error "Heartbeat Timeout" in the CodeDeploy User Guide.
-
-
service_role_arn(Optional[Role], default:None) –A replacement ARN for the service role, if you want to change it.
-
trigger_configurations(Optional[TriggerConfigList], default:None) –Information about triggers to change when the deployment group is updated. For examples, see Edit a Trigger in a CodeDeploy Deployment Group in the CodeDeploy User Guide.
-
alarm_configuration(Optional[AlarmConfiguration], default:None) –Information to add or change about Amazon CloudWatch alarms when the deployment group is updated.
-
auto_rollback_configuration(Optional[AutoRollbackConfiguration], default:None) –Information for an automatic rollback configuration that is added or changed when a deployment group is updated.
-
outdated_instances_strategy(Optional[OutdatedInstancesStrategy], default:None) –Indicates what happens when new Amazon EC2 instances are launched mid-deployment and do not receive the deployed application revision.
If this option is set to
UPDATEor is unspecified, CodeDeploy initiates one or more 'auto-update outdated instances' deployments to apply the deployed application revision to the new Amazon EC2 instances.If this option is set to
IGNORE, CodeDeploy does not initiate a deployment to update the new Amazon EC2 instances. This may result in instances having different revisions. -
deployment_style(Optional[DeploymentStyle], default:None) –Information about the type of deployment, either in-place or blue/green, you want to run and whether to route deployment traffic behind a load balancer.
-
blue_green_deployment_configuration(Optional[BlueGreenDeploymentConfiguration], default:None) –Information about blue/green deployment options for a deployment group.
-
load_balancer_info(Optional[LoadBalancerInfo], default:None) –Information about the load balancer used in a deployment.
-
ec2_tag_set(Optional[EC2TagSet], default:None) –Information about groups of tags applied to on-premises instances. The deployment group includes only Amazon EC2 instances identified by all the tag groups.
-
ecs_services(Optional[ECSServiceList], default:None) –The target Amazon ECS services in the deployment group. This applies only to deployment groups that use the Amazon ECS compute platform. A target Amazon ECS service is specified as an Amazon ECS cluster and service name pair using the format
.: -
on_premises_tag_set(Optional[OnPremisesTagSet], default:None) –Information about an on-premises instance tag set. The deployment group includes only on-premises instances identified by all the tag groups.
-
termination_hook_enabled(Optional[NullableBoolean], default:None) –This parameter only applies if you are using CodeDeploy with Amazon EC2 Auto Scaling. For more information, see Integrating CodeDeploy with Amazon EC2 Auto Scaling in the CodeDeploy User Guide.
Set
terminationHookEnabledtotrueto have CodeDeploy install a termination hook into your Auto Scaling group when you update a deployment group. When this hook is installed, CodeDeploy will perform termination deployments.For information about termination deployments, see Enabling termination deployments during Auto Scaling scale-in events in the CodeDeploy User Guide.
For more information about Auto Scaling scale-in events, see the Scale in topic in the Amazon EC2 Auto Scaling User Guide.
Raises:
-
AlarmsLimitExceededException–The maximum number of alarms for a deployment group (10) was exceeded.
-
ApplicationDoesNotExistException–The application does not exist with the user or Amazon Web Services account.
-
ApplicationNameRequiredException–The minimum number of required application names was not specified.
-
DeploymentConfigDoesNotExistException–The deployment configuration does not exist with the user or Amazon Web Services account.
-
DeploymentGroupAlreadyExistsException–A deployment group with the specified name with the user or Amazon Web Services account already exists.
-
DeploymentGroupDoesNotExistException–The named deployment group with the user or Amazon Web Services account does not exist.
-
DeploymentGroupNameRequiredException–The deployment group name was not specified.
-
ECSServiceMappingLimitExceededException–The Amazon ECS service is associated with more than one deployment groups. An Amazon ECS service can be associated with only one deployment group.
-
InvalidAlarmConfigException–The format of the alarm configuration is invalid. Possible causes include:
-
The alarm list is null.
-
The alarm object is null.
-
The alarm name is empty or null or exceeds the limit of 255 characters.
-
Two alarms with the same name have been specified.
-
The alarm configuration is enabled, but the alarm list is empty.
-
-
InvalidApplicationNameException–The application name was specified in an invalid format.
-
InvalidAutoRollbackConfigException–The automatic rollback configuration was specified in an invalid format. For example, automatic rollback is enabled, but an invalid triggering event type or no event types were listed.
-
InvalidAutoScalingGroupException–The Auto Scaling group was specified in an invalid format or does not exist.
-
InvalidBlueGreenDeploymentConfigurationException–The configuration for the blue/green deployment group was provided in an invalid format. For information about deployment configuration format, see CreateDeploymentConfig.
-
InvalidDeploymentConfigNameException–The deployment configuration name was specified in an invalid format.
-
InvalidDeploymentGroupNameException–The deployment group name was specified in an invalid format.
-
InvalidDeploymentStyleException–An invalid deployment style was specified. Valid deployment types include "IN_PLACE" and "BLUE_GREEN." Valid deployment options include "WITH_TRAFFIC_CONTROL" and "WITHOUT_TRAFFIC_CONTROL."
-
InvalidEC2TagCombinationException–A call was submitted that specified both Ec2TagFilters and Ec2TagSet, but only one of these data types can be used in a single call.
-
InvalidEC2TagException–The tag was specified in an invalid format.
-
InvalidECSServiceException–The Amazon ECS service identifier is not valid.
-
InvalidInputException–The input was specified in an invalid format.
-
InvalidLoadBalancerInfoException–An invalid load balancer name, or no load balancer name, was specified.
-
InvalidOnPremisesTagCombinationException–A call was submitted that specified both OnPremisesTagFilters and OnPremisesTagSet, but only one of these data types can be used in a single call.
-
InvalidRoleException–The service role ARN was specified in an invalid format. Or, if an Auto Scaling group was specified, the specified service role does not grant the appropriate permissions to Amazon EC2 Auto Scaling.
-
InvalidTagException–The tag was specified in an invalid format.
-
InvalidTargetGroupPairException–A target group pair associated with this deployment is not valid.
-
InvalidTrafficRoutingConfigurationException–The configuration that specifies how traffic is routed during a deployment is invalid.
-
InvalidTriggerConfigException–The trigger was specified in an invalid format.
-
LifecycleHookLimitExceededException–The limit for lifecycle hooks was exceeded.
-
TagSetListLimitExceededException–The number of tag groups included in the tag set list exceeded the maximum allowed limit of 3.
-
ThrottlingException–An API function was called too frequently.
-
TriggerTargetsLimitExceededException–The maximum allowed number of triggers was exceeded.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_codedeploy/_services/async_code_deploy.py
3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 3240 3241 3242 3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3336 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 | |