chore(deps): update terraform cloudposse/ecs-alb-service-task/aws to v0.74.0 (release/v1) #262
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.64.1->0.74.0Release Notes
cloudposse/terraform-aws-ecs-alb-service-task (cloudposse/ecs-alb-service-task/aws)
v0.74.0Compare Source
🚀 Enhancements
feat: Add task_definition_arn_without_revision output @adamantike (#216)
what
task_definition_arn_without_revisionoutput, using thearn_without_revisionattribute fromaws_ecs_task_definitionresource.v4.59.0.why
references
v4.59.0: https://github.com/hashicorp/terraform-provider-aws/issues/27119v0.73.0Compare Source
Make `elb_name` optional @lagerfeuer (#215)
what
Make
elb_nameinecs_load_balanceroptional, as described in the linked Terraform docs for ECS Service.why
Currently, when creating a service without
elb_name, Terraform will fail because it expects the variable to be set. The workaround is to set it tonull.references
v0.72.0Compare Source
🚀 Enhancements
feat: support ECS service connect @gberenice (#212)
what
why
references
v0.71.0Compare Source
feat: add pid and ipc mode to task def @dudymas (#206)
what
why
v0.70.0Compare Source
fix external task definition must exist before first run @mightyguava (#204)
what
Change external task definition to a
list(string)so that it can be flagged on without needing the task definition to already exist.why
Fix this issue when using an external task definition
references
Similar to how this was solved for the task role arn https://github.com/cloudposse/terraform-aws-ecs-alb-service-task/blob/main/variables.tf#L216-L226. The workaround for now is to use
-targetlike mentioned in #123.Sync github @max-lobur (#199)
Sync github from the template
v0.69.0Compare Source
v0.68.0Compare Source
Accept map or list for policy arns @Nuru (#198)
what
task_policy_arns_map,task_exec_policy_arns_map) and list (task_policy_arns,task_exec_policy_arns) inputs for policy ARNs. Supersedes and closes #196.depends_onforecs_serviceresource toaws_iam_role_policy.ecs_service.why
History
terraform applyand are therefore not known atplantime, which is a requirement.This Solution
With the solution provided by this PR, any user can avoid #167 by providing a map whose keys are known at plan time, regardless of whether the values are known at plan time. Policy ARNs could be labeled by name, purpose, region, or whatever the user wants to avoid #167. Or, if the user doesn't care about #167, perhaps because they are only supplying a single Policy ARN, then they can just supply it in a list.
v0.67.1Compare Source
🚀 Enhancements
Use map for task & task exec policy arns variables @joe-niland (#194)
what
task_policy_arnsandtask_exec_policy_arnswithtask_policy_arns_mapandtask_exec_policy_arns_maprespectivelyvariables-deprecated.tfand values will be internally converted to a map if variables are definedwhy
references
v0.67.0Compare Source
Add option to trigger a redeployment on apply @joe-niland (#193)
what
why
references
v0.66.4Compare Source
🚀 Enhancements
Task Role uses for-each instead of count @Benbentwo (#178)
what
why
Note:
The outputs had to be changed to output a map as a single string, hence why they look complex, it's to keep backwards compatibility
🐛 Bug Fixes
Task Role uses for-each instead of count @Benbentwo (#178)
what
why
Note:
The outputs had to be changed to output a map as a single string, hence why they look complex, it's to keep backwards compatibility
v0.66.3Compare Source
🚀 Enhancements
make `host_path` optional for fargate @Benbentwo (#176)
what
host_pathas optional in bind_mount_volumes for fargate which it cannot be specifiedwhy
references
v0.66.2Compare Source
Adding support for bind mount volume types @bfox1793 (#173)
what
why
references
🤖 Automatic Updates
Update README.md and docs @cloudpossebot (#171)
what
This is an auto-generated PR that updates the README.md and docs
why
To have most recent changes of README.md and doc from origin templates
v0.66.1Compare Source
🚀 Enhancements
Set bool inputs to type bool @nitrocode (#170)
what
why
ecs_service_enabledusedstringinstead ofbooltypereferences
command
terraform plan -var "ecs_service_enabled=false" -var-file=fixtures.us-east-2.tfvars
v0.66.0Compare Source
Add ecs_service_enabled @nitrocode (#169)
what
why
references
N/A
v0.65.0Compare Source
BUG | Support Dynamic deployment_circuit_breaker for CODE_DEPLOY @lgants (#165)
what
deployment_circuit_breakeroption is now a dynamic block with a conditional for thedeployment_controller_typevaluewhy
CODE_DEPLOYdeployment_circuit_breakeroption.deployment_circuit_breakerwas always included as part of the module. However, the AWS DeploymentCircuitBreaker documentation states":Consequently, when using
CODE_DEPLOYfordeployment_circuit_breakerwith this module, the state is consistently out of sync with the remote, which attempts to sync with the remote on every update.references
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.