CodeDeploy - Boto3 1.38.10 documentation (original) (raw)
Toggle table of contents sidebar
Client¶
class CodeDeploy.Client¶
A low-level client representing AWS CodeDeploy
CodeDeploy is a deployment service that automates application deployments to Amazon EC2 instances, on-premises instances running in your own facility, serverless Lambda functions, or applications in an Amazon ECS service.
You can deploy a nearly unlimited variety of application content, such as an updated Lambda function, updated applications in an Amazon ECS service, code, web and configuration files, executables, packages, scripts, multimedia files, and so on. CodeDeploy can deploy application content stored in Amazon S3 buckets, GitHub repositories, or Bitbucket repositories. You do not need to make changes to your existing code before you can use CodeDeploy.
CodeDeploy makes it easier for you to rapidly release new features, helps you avoid downtime during application deployment, and handles the complexity of updating your applications, without many of the risks associated with error-prone manual deployments.
CodeDeploy Components
Use the information in this guide to help you work with the following CodeDeploy components:
- Application: A name that uniquely identifies the application you want to deploy. CodeDeploy uses this name, which functions as a container, to ensure the correct combination of revision, deployment configuration, and deployment group are referenced during a deployment.
- Deployment group: A set of individual instances, CodeDeploy Lambda deployment configuration settings, or an Amazon ECS service and network details. A Lambda deployment group specifies how to route traffic to a new version of a Lambda function. An Amazon ECS deployment group specifies the service created in Amazon ECS to deploy, a load balancer, and a listener to reroute production traffic to an updated containerized application. An Amazon EC2/On-premises deployment group contains individually tagged instances, Amazon EC2 instances in Amazon EC2 Auto Scaling groups, or both. All deployment groups can specify optional trigger, alarm, and rollback settings.
- Deployment configuration: A set of deployment rules and deployment success and failure conditions used by CodeDeploy during a deployment.
- Deployment: The process and the components used when updating a Lambda function, a containerized application in an Amazon ECS service, or of installing content on one or more instances.
- Application revisions: For an Lambda deployment, this is an AppSpec file that specifies the Lambda function to be updated and one or more functions to validate deployment lifecycle events. For an Amazon ECS deployment, this is an AppSpec file that specifies the Amazon ECS task definition, container, and port where production traffic is rerouted. For an EC2/On-premises deployment, this is an archive file that contains source content—source code, webpages, executable files, and deployment scripts—along with an AppSpec file. Revisions are stored in Amazon S3 buckets or GitHub repositories. For Amazon S3, a revision is uniquely identified by its Amazon S3 object key and its ETag, version, or both. For GitHub, a revision is uniquely identified by its commit ID.
This guide also contains information to help you get details about the instances in your deployments, to make on-premises instances available for CodeDeploy deployments, to get details about a Lambda function deployment, and to get details about Amazon ECS service deployments.
CodeDeploy Information Resources
- CodeDeploy User Guide
- CodeDeploy API Reference Guide
- CLI Reference for CodeDeploy
- CodeDeploy Developer Forum
import boto3
client = boto3.client('codedeploy')
These are the available methods:
- add_tags_to_on_premises_instances
- batch_get_application_revisions
- batch_get_applications
- batch_get_deployment_groups
- batch_get_deployment_instances
- batch_get_deployment_targets
- batch_get_deployments
- batch_get_on_premises_instances
- can_paginate
- close
- continue_deployment
- create_application
- create_deployment
- create_deployment_config
- create_deployment_group
- delete_application
- delete_deployment_config
- delete_deployment_group
- delete_git_hub_account_token
- delete_resources_by_external_id
- deregister_on_premises_instance
- get_application
- get_application_revision
- get_deployment
- get_deployment_config
- get_deployment_group
- get_deployment_instance
- get_deployment_target
- get_on_premises_instance
- get_paginator
- get_waiter
- list_application_revisions
- list_applications
- list_deployment_configs
- list_deployment_groups
- list_deployment_instances
- list_deployment_targets
- list_deployments
- list_git_hub_account_token_names
- list_on_premises_instances
- list_tags_for_resource
- put_lifecycle_event_hook_execution_status
- register_application_revision
- register_on_premises_instance
- remove_tags_from_on_premises_instances
- skip_wait_time_for_instance_termination
- stop_deployment
- tag_resource
- untag_resource
- update_application
- update_deployment_group
Paginators¶
Paginators are available on a client instance via the get_paginator method. For more detailed instructions and examples on the usage of paginators, see the paginators user guide.
The available paginators are:
- ListApplicationRevisions
- ListApplications
- ListDeploymentConfigs
- ListDeploymentGroups
- ListDeploymentInstances
- ListDeploymentTargets
- ListDeployments
- ListGitHubAccountTokenNames
- ListOnPremisesInstances
Waiters¶
Waiters are available on a client instance via the get_waiter method. For more detailed instructions and examples on the usage or waiters, see the waiters user guide.
The available waiters are: