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
Copy file name to clipboardExpand all lines: README.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -137,6 +137,8 @@ No modules.
137
137
| <aname="input_deployment_maximum_percent"></a> [deployment\_maximum\_percent](#input\_deployment\_maximum\_percent)| The upper limit of the number of running tasks that can be running in a service during a deployment |`number`|`200`| no |
138
138
| <aname="input_deployment_minimum_healthy_percent"></a> [deployment\_minimum\_healthy\_percent](#input\_deployment\_minimum\_healthy\_percent)| The lower limit of the number of running tasks that must remain running and healthy in a service during a deployment |`number`|`50`| no |
139
139
| <aname="input_desired_count"></a> [desired\_count](#input\_desired\_count)| The number of instances of the task definitions to place and keep running. |`number`|`1`| no |
140
+
| <aname="input_enable_deployment_circuit_breaker"></a> [enable\_deployment\_circuit\_breaker](#input\_enable\_deployment\_circuit\_breaker)| Whether to enable the deployment circuit breaker logic for the service. |`bool`|`"false"`| no |
141
+
| <aname="input_enable_deployment_circuit_breaker_rollback"></a> [enable\_deployment\_circuit\_breaker\_rollback](#input\_enable\_deployment\_circuit\_breaker\_rollback)| Whether to enable Amazon ECS to roll back the service if a service deployment fails. If rollback is enabled, when a service deployment fails, the service is rolled back to the last deployment that completed successfully. |`bool`|`"false"`| no |
140
142
| <aname="input_enable_execute_command"></a> [enable\_execute\_command](#input\_enable\_execute\_command)| Specifies whether to enable Amazon ECS Exec for the tasks within the service. |`bool`|`true`| no |
141
143
| <aname="input_force_new_deployment"></a> [force\_new\_deployment](#input\_force\_new\_deployment)| Enable to force a new task deployment of the service. This can be used to update tasks to use a newer Docker image with same image/tag combination (e.g. myimage:latest), roll Fargate tasks onto a newer platform version. |`bool`|`false`| no |
142
144
| <aname="input_health_check"></a> [health\_check](#input\_health\_check)| A health block containing health check settings for the target group. Overrides the defaults. |`map(string)`| n/a | yes |
@@ -149,7 +151,7 @@ No modules.
149
151
| <aname="input_placement_constraints"></a> [placement\_constraints](#input\_placement\_constraints)| (Optional) A set of placement constraints rules that are taken into consideration during task placement. Maximum number of placement\_constraints is 10. This is a list of maps, where each map should contain "type" and "expression" |`list(any)`|`[]`| no |
150
152
| <aname="input_platform_version"></a> [platform\_version](#input\_platform\_version)| The platform version on which to run your service. Only applicable for launch\_type set to FARGATE. |`string`|`"LATEST"`| no |
151
153
| <aname="input_private_subnet_ids"></a> [private\_subnet\_ids](#input\_private\_subnet\_ids)| A list of private subnets inside the VPC |`list(string)`| n/a | yes |
152
-
| <aname="input_propogate_tags"></a> [propogate\_tags](#input\_propogate\_tags)| Specifies whether to propagate the tags from the task definition or the service to the tasks. The valid values are SERVICE and TASK\_DEFINITION. |`string`|`"TASK_DEFINITION"`| no |
154
+
| <aname="input_propagate_tags"></a> [propagate\_tags](#input\_propagate\_tags)| Specifies whether to propagate the tags from the task definition or the service to the tasks. The valid values are SERVICE and TASK\_DEFINITION. |`string`|`"TASK_DEFINITION"`| no |
153
155
| <aname="input_proxy_configuration"></a> [proxy\_configuration](#input\_proxy\_configuration)| (Optional) The proxy configuration details for the App Mesh proxy. This is a list of maps, where each map should contain "container\_name", "properties" and "type" |`list(any)`|`[]`| no |
154
156
| <aname="input_repository_credentials"></a> [repository\_credentials](#input\_repository\_credentials)| name or ARN of a secrets manager secret (arn:aws:secretsmanager:region:aws\_account\_id:secret:secret\_name) |`string`|`""`| no |
155
157
| <aname="input_repository_credentials_kms_key"></a> [repository\_credentials\_kms\_key](#input\_repository\_credentials\_kms\_key)| key id, key ARN, alias name or alias ARN of the key that encrypted the repository credentials |`string`|`"alias/aws/secretsmanager"`| no |
@@ -180,7 +182,7 @@ No modules.
180
182
| <aname="input_task_pseudo_terminal"></a> [task\_pseudo\_terminal](#input\_task\_pseudo\_terminal)| Allocate TTY in the container |`bool`|`null`| no |
181
183
| <aname="input_task_start_timeout"></a> [task\_start\_timeout](#input\_task\_start\_timeout)| Time duration (in seconds) to wait before giving up on resolving dependencies for a container. If this parameter is not specified, the default value of 3 minutes is used (fargate). |`number`|`null`| no |
182
184
| <aname="input_task_stop_timeout"></a> [task\_stop\_timeout](#input\_task\_stop\_timeout)| Time duration (in seconds) to wait before the container is forcefully killed if it doesn't exit normally on its own. The max stop timeout value is 120 seconds and if the parameter is not specified, the default value of 30 seconds is used. |`number`|`null`| no |
183
-
| <aname="input_volume"></a> [volume](#input\_volume)| (Optional) A set of volume blocks that containers in your task may use. This is a list of maps, where each map should contain "name", "host\_path", "docker\_volume\_configuration" and "efs\_volume\_configuration". Full set of options can be found at https://www.terraform.io/docs/providers/aws/r/ecs_task_definition.html|`list`|`[]`| no |
185
+
| <aname="input_volume"></a> [volume](#input\_volume)| (Optional) A set of volume blocks that containers in your task may use. This is a list of maps, where each map should contain "name", "host\_path", "docker\_volume\_configuration" and "efs\_volume\_configuration". Full set of options can be found at https://www.terraform.io/docs/providers/aws/r/ecs_task_definition.html|`list(any)`|`[]`| no |
| <aname="input_wait_for_steady_state"></a> [wait\_for\_steady\_state](#input\_wait\_for\_steady\_state)| If true, Terraform will wait for the service to reach a steady state (like aws ecs wait services-stable) before continuing. |`bool`|`false`| no |
description="Whether to enable Amazon ECS to roll back the service if a service deployment fails. If rollback is enabled, when a service deployment fails, the service is rolled back to the last deployment that completed successfully."
description="(Optional) A set of volume blocks that containers in your task may use. This is a list of maps, where each map should contain \"name\", \"host_path\", \"docker_volume_configuration\" and \"efs_volume_configuration\". Full set of options can be found at https://www.terraform.io/docs/providers/aws/r/ecs_task_definition.html"
0 commit comments