Terraform module to provision AWS Code Deploy app and group.
This project is part of our comprehensive "SweetOps" approach towards DevOps.
It's 100% Open Source and licensed under the APACHE2.
We literally have hundreds of terraform modules that are Open Source and well-maintained. Check them out!
Security scanning is graciously provided by Bridgecrew. Bridgecrew is the leading fully hosted, cloud-native solution providing continuous Terraform security and compliance.
IMPORTANT: We do not pin modules to versions in our examples because of the difficulty of keeping the versions in the documentation in sync with the latest released versions. We highly recommend that in your code you pin the version to the exact version you are using so that your infrastructure remains stable, and update versions in a systematic way so that they do not catch you by surprise.
Also, because of a bug in the Terraform registry (hashicorp/terraform#21417), the registry shows many of our inputs as required when in fact they are optional. The table below correctly indicates which inputs are required.
For a complete example, see examples/complete.
For automated tests of the complete example using bats and Terratest (which tests and deploys the example on AWS), see test.
module "example" {
source = "cloudposse/code-deploy/aws"
# Cloud Posse recommends pinning every module to a specific version
# version = "x.x.x"
}
Here is an example of using this module:
examples/complete
- complete example of using this module
Available targets:
help Help screen
help/all Display help for all targets
help/short This help short screen
lint Lint terraform code
Name | Version |
---|---|
terraform | >= 0.13 |
aws | >= 2.0 |
local | >= 1.2 |
Name | Version |
---|---|
aws | >= 2.0 |
Name | Source | Version |
---|---|---|
sns_topic | cloudposse/sns-topic/aws | 0.16.0 |
this | cloudposse/label/null | 0.24.1 |
Name | Type |
---|---|
aws_codedeploy_app.default | resource |
aws_codedeploy_deployment_config.default | resource |
aws_codedeploy_deployment_group.default | resource |
aws_iam_role.default | resource |
aws_iam_role_policy_attachment.default | resource |
aws_iam_policy_document.assume_role | data source |
Name | Description | Type | Default | Required |
---|---|---|---|---|
additional_tag_map | Additional tags for appending to tags_as_list_of_maps. Not added to tags . |
map(string) |
{} |
no |
alarm_configuration | Configuration of deployment to stop when a CloudWatch alarm detects that a metric has fallen below or exceeded a defined threshold. alarms: A list of alarms configured for the deployment group. ignore_poll_alarm_failure: Indicates whether a deployment should continue if information about the current state of alarms cannot be retrieved from CloudWatch. |
object({ |
null |
no |
attributes | Additional attributes (e.g. 1 ) |
list(string) |
[] |
no |
auto_rollback_configuration_events | The event type or types that trigger a rollback. Supported types are DEPLOYMENT_FAILURE and DEPLOYMENT_STOP_ON_ALARM . |
string |
"DEPLOYMENT_FAILURE" |
no |
autoscaling_groups | A list of Autoscaling Groups associated with the deployment group. | list(string) |
[] |
no |
blue_green_deployment_config | Configuration block of the blue/green deployment options for a deployment group, see https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/codedeploy_deployment_group#blue_green_deployment_config |
any |
null |
no |
compute_platform | The compute platform can either be ECS , Lambda , or Server |
string |
"ECS" |
no |
context | Single object for setting entire context at once. See description of individual variables for details. Leave string and numeric variables as null to use default value.Individual variable settings (non-null) override settings in context object, except for attributes, tags, and additional_tag_map, which are merged. |
any |
{ |
no |
create_default_service_role | Whether to create default IAM role ARN that allows deployments. | bool |
true |
no |
create_default_sns_topic | Whether to create default SNS topic through which notifications are sent. | bool |
true |
no |
delimiter | Delimiter to be used between namespace , environment , stage , name and attributes .Defaults to - (hyphen). Set to "" to use no delimiter at all. |
string |
null |
no |
deployment_style | Configuration of the type of deployment, either in-place or blue/green, you want to run and whether to route deployment traffic behind a load balancer. deployment_option: Indicates whether to route deployment traffic behind a load balancer. Possible values: WITH_TRAFFIC_CONTROL , WITHOUT_TRAFFIC_CONTROL .deployment_type: Indicates whether to run an in-place deployment or a blue/green deployment. Possible values: IN_PLACE , BLUE_GREEN . |
object({ |
null |
no |
ec2_tag_filter | A list of sets of tag filters. If multiple tag groups are specified, any instance that matches to at least one tag filter of every tag group is selected. key: The key of the tag filter. type: The type of the tag filter, either KEY_ONLY , VALUE_ONLY , or KEY_AND_VALUE .value: The value of the tag filter. |
list(object({ |
null |
no |
ecs_service | Configuration block(s) of the ECS services for a deployment group. cluster_name: The name of the ECS cluster. service_name: The name of the ECS service. |
list(object({ |
null |
no |
enabled | Set to false to prevent the module from creating any resources | bool |
null |
no |
environment | Environment, e.g. 'uw2', 'us-west-2', OR 'prod', 'staging', 'dev', 'UAT' | string |
null |
no |
id_length_limit | Limit id to this many characters (minimum 6).Set to 0 for unlimited length.Set to null for default, which is 0 .Does not affect id_full . |
number |
null |
no |
label_key_case | The letter case of label keys (tag names) (i.e. name , namespace , environment , stage , attributes ) to use in tags .Possible values: lower , title , upper .Default value: title . |
string |
null |
no |
label_order | The naming order of the id output and Name tag. Defaults to ["namespace", "environment", "stage", "name", "attributes"]. You can omit any of the 5 elements, but at least one must be present. |
list(string) |
null |
no |
label_value_case | The letter case of output label values (also used in tags and id ).Possible values: lower , title , upper and none (no transformation).Default value: lower . |
string |
null |
no |
load_balancer_info | Single configuration block of the load balancer to use in a blue/green deployment, see https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/codedeploy_deployment_group#load_balancer_info |
map(any) |
null |
no |
minimum_healthy_hosts | type: The type can either be FLEET_PERCENT or HOST_COUNT .value: The value when the type is FLEET_PERCENT represents the minimum number of healthy instances as a percentage of the total number of instances in the deployment. When the type is HOST_COUNT , the value represents the minimum number of healthy instances as an absolute value. |
object({ |
null |
no |
name | Solution name, e.g. 'app' or 'jenkins' | string |
null |
no |
namespace | Namespace, which could be your organization name or abbreviation, e.g. 'eg' or 'cp' | string |
null |
no |
regex_replace_chars | Regex to replace chars with empty string in namespace , environment , stage and name .If not set, "/[^a-zA-Z0-9-]/" is used to remove all characters other than hyphens, letters and digits. |
string |
null |
no |
service_role_arn | The service IAM role ARN that allows deployments. | string |
null |
no |
sns_topic_arn | The ARN of the SNS topic through which notifications are sent. | string |
null |
no |
stage | Stage, e.g. 'prod', 'staging', 'dev', OR 'source', 'build', 'test', 'deploy', 'release' | string |
null |
no |
tags | Additional tags (e.g. map('BusinessUnit','XYZ') |
map(string) |
{} |
no |
traffic_routing_config | type: Type of traffic routing config. One of TimeBasedCanary , TimeBasedLinear , AllAtOnce .interval: The number of minutes between the first and second traffic shifts of a deployment. percentage: The percentage of traffic to shift in the first increment of a deployment. |
object({ |
null |
no |
trigger_events | The event type or types for which notifications are triggered. Some values that are supported: DeploymentStart , DeploymentSuccess , DeploymentFailure , DeploymentStop , DeploymentRollback , InstanceStart , InstanceSuccess , InstanceFailure . See the CodeDeploy documentation for all possible values. http://docs.aws.amazon.com/codedeploy/latest/userguide/monitoring-sns-event-notifications-create-trigger.html |
list(string) |
[ |
no |
Name | Description |
---|---|
deployment_config_id | The deployment config ID. |
deployment_config_name | The deployment group's config name. |
group_id | The application group ID. |
id | The application ID. |
name | The application's name. |
Like this project? Please give it a ★ on our GitHub! (it helps us a lot)
Are you using this project or any of our other projects? Consider leaving a testimonial. =)
Check out these related projects.
- terraform-aws-sns-topic - Terraform Module to Provide an Amazon Simple Notification Service (SNS)
- terraform-null-label - Terraform Module to define a consistent naming convention by (namespace, stage, name, [attributes])
- terraform-aws-codebuild - Terraform Module to easily leverage AWS CodeBuild for Continuous Integration
- terraform-aws-codepipeline-codedeploy - Terraform module that generates an AWS Codepipeline, and deploys via CodeDeploy
- terraform-aws-codefresh-backing-services - Terraform module to provision AWS backing services necessary to run Codefresh Enterprise
- terraform-aws-code-deploy - %!s()
For additional context, refer to some of these links.
- terraform-provider-aws - Terraform AWS provider
- terraform-provider-local - Terraform local provider – Used to manage local resources, such as creating files.
Got a question? We got answers.
File a GitHub issue, send us an email or join our Slack Community.
We are a DevOps Accelerator. We'll help you build your cloud infrastructure from the ground up so you can own it. Then we'll show you how to operate it and stick around for as long as you need us.
Work directly with our team of DevOps experts via email, slack, and video conferencing.
We deliver 10x the value for a fraction of the cost of a full-time engineer. Our track record is not even funny. If you want things done right and you need it done FAST, then we're your best bet.
- Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.
- Release Engineering. You'll have end-to-end CI/CD with unlimited staging environments.
- Site Reliability Engineering. You'll have total visibility into your apps and microservices.
- Security Baseline. You'll have built-in governance with accountability and audit logs for all changes.
- GitOps. You'll be able to operate your infrastructure via Pull Requests.
- Training. You'll receive hands-on training so your team can operate what we build.
- Questions. You'll have a direct line of communication between our teams via a Shared Slack channel.
- Troubleshooting. You'll get help to triage when things aren't working.
- Code Reviews. You'll receive constructive feedback on Pull Requests.
- Bug Fixes. We'll rapidly work with you to fix any bugs in our projects.
Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.
Participate in our Discourse Forums. Here you'll find answers to commonly asked questions. Most questions will be related to the enormous number of projects we support on our GitHub. Come here to collaborate on answers, find solutions, and get ideas about the products and services we value. It only takes a minute to get started! Just sign in with SSO using your GitHub account.
Sign up for our newsletter that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.
Join us every Wednesday via Zoom for our weekly "Lunch & Learn" sessions. It's FREE for everyone!
Please use the issue tracker to report any bugs or file feature requests.
If you are interested in being a contributor and want to get involved in developing this project or help out with our other projects, we would love to hear from you! Shoot us an email.
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
- Fork the repo on GitHub
- Clone the project to your own machine
- Commit changes to your own branch
- Push your work back up to your fork
- Submit a Pull Request so that we can review your changes
NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!
Copyright © 2020-2021 Cloud Posse, LLC
See LICENSE for full details.
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
https://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
All other trademarks referenced herein are the property of their respective owners.
This project is maintained and funded by Cloud Posse, LLC. Like it? Please let us know by leaving a testimonial!
We're a DevOps Professional Services company based in Los Angeles, CA. We ❤️ Open Source Software.
We offer paid support on all of our projects.
Check out our other projects, follow us on twitter, apply for a job, or hire us to help with your cloud strategy and implementation.
Vladimir Syromyatnikov |
RB |
---|