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
chore(ecs-patterns): revert "feature flag missing for breaking change passing container port for target group port (#20284)" (#20430)
This reverts #20284 since its tests fail to pass in CDK v2, blocking the next CDK release. The root cause of failure looks as though it may be the same as #20427 - I've included the test logs below:
<details>
```
@aws-cdk/aws-ecs-patterns: FAIL test/fargate/load-balanced-fargate-service-v2.test.js (11.703 s)
@aws-cdk/aws-ecs-patterns: � When Network Load Balancer › Fargate networkloadbalanced construct uses custom Port for target group when feature flag is enabled
@aws-cdk/aws-ecs-patterns: Template has 1 resources with type AWS::ElasticLoadBalancingV2::TargetGroup, but none match as expected.
@aws-cdk/aws-ecs-patterns: The closest result is:
@aws-cdk/aws-ecs-patterns: {
@aws-cdk/aws-ecs-patterns: "Type": "AWS::ElasticLoadBalancingV2::TargetGroup",
@aws-cdk/aws-ecs-patterns: "Properties": {
@aws-cdk/aws-ecs-patterns: "Port": 80,
@aws-cdk/aws-ecs-patterns: "Protocol": "TCP",
@aws-cdk/aws-ecs-patterns: "TargetType": "ip",
@aws-cdk/aws-ecs-patterns: "VpcId": {
@aws-cdk/aws-ecs-patterns: "Ref": "VPCB9E5F0B4"
@aws-cdk/aws-ecs-patterns: }
@aws-cdk/aws-ecs-patterns: }
@aws-cdk/aws-ecs-patterns: }
@aws-cdk/aws-ecs-patterns: with the following mismatches:
@aws-cdk/aws-ecs-patterns: Expected 81 but received 80 at /Properties/Port (using objectLike matcher)
@aws-cdk/aws-ecs-patterns: 83 | const matchError = hasResourceProperties(this.template, type, props);
@aws-cdk/aws-ecs-patterns: 84 | if (matchError) {
@aws-cdk/aws-ecs-patterns: > 85 | throw new Error(matchError);
@aws-cdk/aws-ecs-patterns: | ^
@aws-cdk/aws-ecs-patterns: 86 | }
@aws-cdk/aws-ecs-patterns: 87 | }
@aws-cdk/aws-ecs-patterns: 88 |
@aws-cdk/aws-ecs-patterns: at Template.hasResourceProperties (../assertions/lib/template.ts:85:13)
@aws-cdk/aws-ecs-patterns: at fn (test/fargate/load-balanced-fargate-service-v2.test.ts:709:31)
@aws-cdk/aws-ecs-patterns: at Object.<anonymous> (../../../tools/@aws-cdk/cdk-build-tools/lib/feature-flag.ts:34:35)
@aws-cdk/aws-ecs-patterns: � When Network Load Balancer › test Fargate multinetworkloadbalanced construct uses custom Port for target group when feature flag is enabled
@aws-cdk/aws-ecs-patterns: Template has 2 resources with type AWS::ElasticLoadBalancingV2::TargetGroup, but none match as expected.
@aws-cdk/aws-ecs-patterns: The closest result is:
@aws-cdk/aws-ecs-patterns: {
@aws-cdk/aws-ecs-patterns: "Type": "AWS::ElasticLoadBalancingV2::TargetGroup",
@aws-cdk/aws-ecs-patterns: "Properties": {
@aws-cdk/aws-ecs-patterns: "Port": 80,
@aws-cdk/aws-ecs-patterns: "Protocol": "TCP",
@aws-cdk/aws-ecs-patterns: "TargetType": "ip",
@aws-cdk/aws-ecs-patterns: "VpcId": {
@aws-cdk/aws-ecs-patterns: "Ref": "VPCB9E5F0B4"
@aws-cdk/aws-ecs-patterns: }
@aws-cdk/aws-ecs-patterns: }
@aws-cdk/aws-ecs-patterns: }
@aws-cdk/aws-ecs-patterns: with the following mismatches:
@aws-cdk/aws-ecs-patterns: Expected 81 but received 80 at /Properties/Port (using objectLike matcher)
@aws-cdk/aws-ecs-patterns: 83 | const matchError = hasResourceProperties(this.template, type, props);
@aws-cdk/aws-ecs-patterns: 84 | if (matchError) {
@aws-cdk/aws-ecs-patterns: > 85 | throw new Error(matchError);
@aws-cdk/aws-ecs-patterns: | ^
@aws-cdk/aws-ecs-patterns: 86 | }
@aws-cdk/aws-ecs-patterns: 87 | }
@aws-cdk/aws-ecs-patterns: 88 |
@aws-cdk/aws-ecs-patterns: at Template.hasResourceProperties (../assertions/lib/template.ts:85:13)
@aws-cdk/aws-ecs-patterns: at fn (test/fargate/load-balanced-fargate-service-v2.test.ts:823:31)
@aws-cdk/aws-ecs-patterns: at Object.<anonymous> (../../../tools/@aws-cdk/cdk-build-tools/lib/feature-flag.ts:34:35)
```
</details>
----
### All Submissions:
* [ ] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md)
### Adding new Unconventional Dependencies:
* [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/master/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/master/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*
testFutureBehavior('Fargate networkloadbalanced construct uses custom Port for target group when feature flag is enabled',{[ECS_PATTERNS_TARGET_GROUP_PORT_FROM_CONTAINER_PORT]: true},App,(app)=>{
testFutureBehavior('Fargate networkloadbalanced construct uses 80 for target group when feature flag is enabled but container port is not provided',{[ECS_PATTERNS_TARGET_GROUP_PORT_FROM_CONTAINER_PORT]: true},App,(app)=>{
testFutureBehavior('test Fargate multinetworkloadbalanced construct uses custom Port for target group when feature flag is enabled',{[ECS_PATTERNS_TARGET_GROUP_PORT_FROM_CONTAINER_PORT]: true},App,(app)=>{
693
+
test('test Fargate multinetworkloadbalanced construct with custom Port',()=>{
testFutureBehavior('test Fargate multinetworkloadbalanced construct uses 80 for target group when feature flag is enabled but container port is not provided',{[ECS_PATTERNS_TARGET_GROUP_PORT_FROM_CONTAINER_PORT]: true},App,(app)=>{
0 commit comments