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
This wercker step allows to deploy applications with [AWS Code Deploy](http://docs.aws.amazon.com/codedeploy/latest/userguide/welcome.html) service.
5
7
6
8
Please read the [AWS Code Deploy](http://docs.aws.amazon.com/codedeploy/latest/userguide/welcome.html) documentation and [API](http://docs.aws.amazon.com/cli/latest/reference/deploy/index.html) before using this step.
7
9
8
-
This step use the [AWS Cli](http://docs.aws.amazon.com/cli/latest/reference/), so you have to use this step with a box where AWS Cli is already installed
9
-
or install AWS Cli with this Wercker step : [EdgecaseInc/wercker-step-install-aws-cli](https://github.com/EdgecaseInc/wercker-step-install-aws-cli).
10
-
11
10
## AWS Code Deploy workflow
12
11
13
12
To deploy an application with AWS Code Deploy, the Wercker step follow this steps :
The second step consists on creating a deployment config. This step is totally *optional* because you can use the deployment strategy already defined in Code Deploy.
35
+
This step consists on creating a deployment config. This step is totally *optional* because you can use the deployment strategy already defined in Code Deploy.
27
36
28
-
The following configuration allows to configure this step :
37
+
The following configuration allows to setup this step :
29
38
30
-
*`deployment-config-name` (optional) Deployment config name. By default : _CodeDeployDefault.OneAtATime_
31
-
*`minimum-healthy-hosts` (optional) The minimum number of healthy instances during deployment. By default : _type=FLEET_PERCENT,value=75_
39
+
*`deployment-config-name` (optional): Deployment config name. By default : _CodeDeployDefault.OneAtATime_
40
+
*`minimum-healthy-hosts` (optional): The minimum number of healthy instances during deployment. By default : _type=FLEET_PERCENT,value=75_
The third step consists on defining a deployment group. If the deployment group provided does not exists this step create a deployment group in Code Deploy.
44
+
This step consists on defining a deployment group. If the deployment group provided does not exists this step create a deployment group in Code Deploy.
36
45
37
-
The following configuration allows to configure this step :
46
+
The following configuration allows to setup this step :
38
47
39
-
*`deployment-group-name` (required) Deployment group name
40
-
*`service-role-arn` (optional) Service role arn giving permissions to use Code Deploy when creating a deployment group
41
-
*`ec2-tag-filters` (optional) EC2 tags to filter on when creating a deployment group
42
-
*`auto-scaling-groups` (optional) Auto Scaling groups when creating a deployment group
48
+
*`deployment-group-name` (required): Deployment group name
49
+
*`service-role-arn` (optional): Service role arn giving permissions to use Code Deploy when creating a deployment group
50
+
*`ec2-tag-filters` (optional): EC2 tags to filter on when creating a deployment group
51
+
*`auto-scaling-groups` (optional): Auto Scaling groups when creating a deployment group
43
52
44
-
#### Step 4 : [Pushing to S3](http://docs.aws.amazon.com/cli/latest/reference/deploy/push.html)
53
+
#### Step 5 : [Pushing to S3](http://docs.aws.amazon.com/cli/latest/reference/deploy/push.html)
45
54
46
55
This step consists to push the application to S3.
47
56
48
-
The following configuration allows to configure this step :
57
+
The following configuration allows to setup this step :
49
58
50
-
*`s3-bucket` (required) S3 Bucket
51
-
*`s3-source` (optional) S3 Source. By default : _._
52
-
*`s3-key` (optional) S3 Key. By default: _{application-name}_
59
+
*`s3-bucket` (required): S3 Bucket
60
+
*`s3-source` (optional): S3 Source. By default : _._
61
+
*`s3-key` (optional): S3 Key. By default: _{application-name}_
0 commit comments