-
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-ecs-patterns: Trying to pass a Queue into QueueProcessingFargateService errors #3579
Comments
@eladb, @NGL321 looks like this might be related to JSII and not to the ECS construct itself. The following in typescript works: const vpc = new ec2.Vpc(stack, 'MyVpc', { maxAzs: 2 });
const cluster = new ecs.Cluster(stack, 'Cluster', { vpc });
const queue = new Queue(stack, 'queue', {});
new ecs_patterns.QueueProcessingFargateService(stack, "FargateService", {
cluster,
image: ecs.ContainerImage.fromAsset(path.resolve(__dirname, 'local-image')),
queue,
}); |
Yeah this is clearly a JSII issue. This may have been fixed in the latest |
Relates #2375 Same root cause, Correctly deserialize callback arguments #404 |
Might be fixed in the next CDK release! |
Confirmed fixed in CDK |
Using the .NET CDK,
results in the following error:
Removing the Queue argument resolves the exception.
What is the expected behavior (or behavior of feature suggested)?
I should be able to specify a queue construct to use.
What is the motivation / use case for changing the behavior or adding this feature?
It's a bug. Documentation says this should work.
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: