-
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-lib.aws_ecs_patterns: unable to set value of idle_timeout to value greater than Duration.seconds(400) #21560
Labels
@aws-cdk/aws-ecs-patterns
Related to ecs-patterns library
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
p2
Comments
emossman
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
Aug 11, 2022
peterwoodworth
added
@aws-cdk/aws-ecs-patterns
Related to ecs-patterns library
p2
effort/small
Small work item – less than a day of effort
and removed
aws-cdk-lib
Related to the aws-cdk-lib package
needs-triage
This issue or PR still needs to be triaged.
labels
Aug 12, 2022
4 tasks
I think this is because the duration isn't getting converted. I've submitted a PR for this, thanks for reporting! |
mergify bot
pushed a commit
that referenced
this issue
Aug 14, 2022
…1584) fixes #21560 Duration wasn't getting compared correctly and prevented values above 400 from getting used for `ApplicationLoadBalancedService.idleTimeout` ---- ### All Submissions: * [ ] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
josephedward
pushed a commit
to josephedward/aws-cdk
that referenced
this issue
Aug 30, 2022
…s#21584) fixes aws#21560 Duration wasn't getting compared correctly and prevented values above 400 from getting used for `ApplicationLoadBalancedService.idleTimeout` ---- ### All Submissions: * [ ] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-ecs-patterns
Related to ecs-patterns library
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
p2
Describe the bug
I have an ALB created via the aws_ecs_patterns.ApplicationLoadBalancedFargateService class with a default idle_timeout that I would like to modify to 700 seconds.
Given the following sanitized fargate service:
I get the following trimmed output:
This same error is observed for any values >
Duration.seconds(400)
.Expected Behavior
I expected the idle_timeout of my load balancer to be set to 700 seconds.
Current Behavior
A JSII error is thrown:
Reproduction Steps
Possible Solution
This upper limit of 400 seconds is 10% of the actual upper limit of idle timeout, which suggests a zero was omitted somwehere.
Looking at this commit 546581a#diff-bc0826ed8167fb2e85180ae376629e966a9d26b7205641b5ca1f51a1a6f3d150R446 it seems that the upper limit of idle_timeout was set properly, but there could be something else I'm running into.
Additional Information/Context
Setting the value of idle_timeout to a
Duration.minutes(int)
also gives the same error.Using the workaround specified in this comment #12913 (comment) works for me.
CDK CLI Version
2.37.0 (build aba5ef6)
Framework Version
No response
Node.js Version
v18.4.0
OS
macOS 12.5 (21G72)
Language
Python
Language Version
3.9.13
Other information
#12913
#21261
The text was updated successfully, but these errors were encountered: