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
When specifying an EFS Volume configuration in var.volumes, this gets handed to the cloudposse/ecs-alb-service-task/aws module via its variable var.docker_volumes, in which the EFS part will be dropped.
If my reading of this repo is correct the bug was caused in
Describe the Bug
When specifying an EFS Volume configuration in var.volumes, this gets handed to the
cloudposse/ecs-alb-service-task/aws
module via its variablevar.docker_volumes
, in which the EFS part will be dropped.If my reading of this repo is correct the bug was caused in
23c9105
through an automated update caused by a variable refactoring in the
ecs-alb-service-task
module.cloudposse/terraform-aws-ecs-alb-service-task@4294ee2
Expected Behavior
Passing the
efs_volume_configuration
list of maps will create an EFS Volume Configuration in the Task DefinitionSteps to Reproduce
Create a VPC, Subnet, ALB, EFS volume, then try to pass the latter into a container.
A module call like this should create an EFS Volume configuration
Screenshots
No response
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: