When the deployment controller type is set to CODE_DEPLOY, the wait for ECS service creation does not complete about ecspresso

[hrfmmr]

@fujiwara I tried and it works! 🙌
Thank you for fixing so fast!

log

module.ecs.null_resource.ecspresso_***: Creating...
module.ecs.null_resource.ecspresso_***: Provisioning with 'local-exec'...
module.ecs.null_resource.ecspresso_*** (local-exec): Executing: ["/bin/sh" "-c" "~/bin/ecspresso version && ~/bin/ecspresso deploy --debug"]
module.ecs.null_resource.ecspresso_*** (local-exec): ecspresso v2.0.3+nightly-1a317daaa2d74e9dccb2428791be433c21152384
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:05 ***-service/***-cluster [DEBUG] config file path: ecspresso.yml
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:05 ***-service/***-cluster [DEBUG] dispatching subcommand: deploy
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:05 ***-service/***-cluster [DEBUG] deploy
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:05 [DEBUG] {"DryRun":false,"DesiredCount":-1,"SkipTaskDefinition":false,"ForceNewDeployment":false,"NoWait":false,"SuspendAutoScaling":null,"ResumeAutoScaling":null,"RollbackEvents":"","UpdateService":true,"LatestTaskDefinition":false}
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:05 ***-service/***-cluster Starting deploy module.ecs.aws_lb_listener.internal_blue: Creation complete after 0s [id=arn:aws:elasticloadbalancing:ap-northeast-1:190162224208:listener/app/***-alb-internal/d4e22366f5091ea2/16747bc45e114036]
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:05 ***-service/***-cluster Service ***-service not found. Creating a new service
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:05 ***-service/***-cluster Starting create service
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:05 ***-service/***-cluster [DEBUG] Loaded DesiredCount: 2
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:05 ***-service/***-cluster Registering a new task definition...
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:05 ***-service/***-cluster Task definition is registered ***-def:35
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:06 ***-service/***-cluster Service is created
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:09 ***-service/***-cluster [DEBUG] service ***-service is ACTIVE
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:09 ***-service/***-cluster [DEBUG] wait for CodeDeploy
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:09 ***-service/***-cluster [DEBUG] find applications in CodeDeploy
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:09 ***-service/***-cluster [DEBUG] found CodeDeploy applications: [***-codedeploy]
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:09 ***-service/***-cluster [DEBUG] application ***-codedeploy compute platform ECS
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:09 ***-service/***-cluster [DEBUG] CodeDeploy found deploymentGroups: []
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:09 ***-service/***-cluster [INFO] failed to find CodeDeploy Application/DeploymentGroup for ECS service ***-service on cluster ***-cluster
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:09 ***-service/***-cluster [DEBUG] service ***-service is ACTIVE
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:09 ***-service/***-cluster Waiting a task set PRIMARY stable: STABILIZING
module.ecs.null_resource.ecspresso_***: Still creating... [10s elapsed]
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:20 ***-service/***-cluster [DEBUG] service ***-service is ACTIVE
module.ecs.null_resource.ecspresso_***: Still creating... [20s elapsed]
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:30 ***-service/***-cluster [DEBUG] service ***-service is ACTIVE
module.ecs.null_resource.ecspresso_***: Still creating... [30s elapsed]
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:40 ***-service/***-cluster [DEBUG] service ***-service is ACTIVE
module.ecs.null_resource.ecspresso_***: Still creating... [40s elapsed]
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:04:50 ***-service/***-cluster [DEBUG] service ***-service is ACTIVE
module.ecs.null_resource.ecspresso_***: Still creating... [50s elapsed]
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:05:00 ***-service/***-cluster [DEBUG] service ***-service is ACTIVE
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:05:00 ***-service/***-cluster Waiting a task set PRIMARY stable: STEADY_STATE
module.ecs.null_resource.ecspresso_*** (local-exec): 2023/01/14 12:05:00 ***-service/***-cluster Service is stable now. Completed!
module.ecs.null_resource.ecspresso_***: Creation complete after 55s [id=8295189575364490852]
module.ecs.data.aws_ecs_service.***_backend: Reading...
module.ecs.data.aws_ecs_service.***_backend: Read complete after 1s [id=arn:aws:ecs:ap-northeast-1:190162224208:service/***-cluster/***-service]
module.ecs.aws_codedeploy_deployment_group.***: Creating...
module.ecs.aws_codedeploy_deployment_group.***: Creation complete after 1s [id=beab2ebd-0b92-49d3-8459-6754253c6f42]

[fujiwara]

@hrfmmr v2.0.4 released! https://github.com/kayac/ecspresso/releases/tag/v2.0.4

[fujiwara]

@hrfmmr Thank you for reporting!
I fixed this issue by #502.

Could you try this binary? https://github.com/kayac/ecspresso/releases/tag/v2.0.3-2-g7a04e2d-15-g5479761

[hrfmmr]

@fujiwara Awesome! Thank you!
I'll try it 👍

[hrfmmr]

I tried, but it seems to expect the deployment group to exist when creating the ECS service, and it failed.

│ Error running command '~/bin/ecspresso version && ~/bin/ecspresso deploy --debug': exit status 1. Output: ecspresso v2.0.3+2-g7a04e2d-15-g5479761
│ 2023/01/12 07:04:00 ***-service/***-cluster [DEBUG] config file path: ecspresso.yml
│ 2023/01/12 07:04:00 ***-service/***-cluster [DEBUG] dispatching subcommand: deploy
│ 2023/01/12 07:04:00 ***-service/***-cluster [DEBUG] deploy
│ 2023/01/12 07:04:00 [DEBUG]
│ {"DryRun":false,"DesiredCount":-1,"SkipTaskDefinition":false,"ForceNewDeployment":false,"NoWait":false,"SuspendAutoScaling":null,"ResumeAutoScaling":null,"RollbackEvents":"","Up
dateService":true,"LatestTaskDefinition":false}
│ 2023/01/12 07:04:00 ***-service/***-cluster Starting deploy
│ 2023/01/12 07:04:00 ***-service/***-cluster Service ***-service not found. Creating a new service
│ 2023/01/12 07:04:00 ***-service/***-cluster Starting create service
│ 2023/01/12 07:04:00 ***-service/***-cluster [DEBUG] Loaded DesiredCount: 2
│ 2023/01/12 07:04:01 ***-service/***-cluster Registering a new task definition...
│ 2023/01/12 07:04:01 ***-service/***-cluster Task definition is registered ***-def:33
│ 2023/01/12 07:04:02 ***-service/***-cluster Service is created
│ 2023/01/12 07:04:05 ***-service/***-cluster [DEBUG] service ***-service is ACTIVE
│ 2023/01/12 07:04:05 ***-service/***-cluster [DEBUG] wait for CodeDeploy
│ 2023/01/12 07:04:05 ***-service/***-cluster [DEBUG] find applications in CodeDeploy
│ 2023/01/12 07:04:05 ***-service/***-cluster [DEBUG] found CodeDeploy applications: [test-codedeploy-app ***-codedeploy]
│ 2023/01/12 07:04:05 ***-service/***-cluster [DEBUG] application test-codedeploy-app compute platform ECS
│ 2023/01/12 07:04:05 ***-service/***-cluster [DEBUG] application ***-codedeploy compute platform ECS
│ 2023/01/12 07:04:05 ***-service/***-cluster [DEBUG] CodeDeploy found deploymentGroups: []
│ 2023/01/12 07:04:05 ***-service/***-cluster [DEBUG] CodeDeploy found deploymentGroups: []
│ 2023/01/12 07:04:05 [ERROR] FAILED. failed to find CodeDeploy Application/DeploymentGroup for ECS service ***-service on cluster ***-cluster
│

[hrfmmr]

expect the deployment group to exist

In order to create a CodeDeploy deployment group, an ECS service must be created first, right?

[fujiwara]

@hrfmmr

In order to create a CodeDeploy deployment group, an ECS service must be created first, right?

Yes, right.

But after a deployment group is created, a related ECS service can delete and re-create. I've tested this case only, but it is insufficient.

I'll fix to not needing a deployment group on creating an ECS service.

[fujiwara]

@hrfmmr
Fixed in this version. This version can wait to create an ECS service whether related CodeDeploy resources exist.
Please try again!
https://github.com/kayac/ecspresso/releases/tag/v2.0.3-nightly-97054235af9e9f9b60a0d337ebdab5f80019b91d