-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@aws-cdk/aws-ecs-patterns: minScalingCapacity cannot be set to 0 #15632
Comments
Hey @paya-cz, would you like to submit a pr for this? |
@peterwoodworth I tried to, but it looks like getting the dev environment up and running is quite a bit more involved than I hoped for. I opened the repo in Gitpod, but the build returned error code 1 with the error message being buried somewhere deep in the log and not available in the terminal anymore. Trying to run As a last resort, I did Seems to me the contributing guide is either outdated, or I must have missed some step? Although I imagine the point of Gitpod is that everything should work out of the box. So I don't think I will be able to submit a PR for this. |
I've never used the Gitpod method, so I don't think I'll be able to troubleshoot that for you. Have you tried the other method of submitting PRs? I could help you with that if you'd like. If not, I can try to get a PR up for this when I have the time |
@peterwoodworth I see you already made a PR for this, thank you for handling this issue. I use Windows VM for development, I guess I might be able to get WSL setup in order to contribute to the project, but unfortunately don't really have time to play with that at the moment. Gitpod would solve this friction beautifully though if it worked :-) |
|
Reproduction Steps
It is impossible to set
minScalingCapacity
on a SQS-processing Fargate task to0
, because of this check:aws-cdk/packages/@aws-cdk/aws-ecs-patterns/lib/base/queue-processing-service-base.ts
Line 315 in 2647cf3
The operator
||
treats0
as a falsy value. Use??
instead. A workaround seems to be to setdesiredTaskCount
deprecated prop to0
, since that's used in the falsy branch path.What did you expect to happen?
minScalingCapacity
set to 0 should deploy autoscaling with minimum tasks: 0.What actually happened?
minScalingCapacity
set to 0 deploys ECS autoscaling with minimum tasks: 1.Environment
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: