I see the property here: https://pulumi.io/reference/pkg/nodejs/@pulumi/aws/ecs/#property-ulimits but don't see it here https://pulumi.io/reference/pkg/nodejs/@pulumi/cloud-aws/index.html#Service.

This is a current limitation of

cloudaws.Service

unfortunately. It's tracked by https://github.com/pulumi/pulumi-cloud/issues/91. This particular one is likely quite easy to add. If you are interested in submitting a PR, we'd be happy to accept it - else I'll see if we can get this (and other similar low hanging fruit for container options) added soon. Note that we're also working on an API that will be more "ECS-native" but still offer the high-level benefits of

cloudaws.Service

- while not having these sharp edges. I'll reach out with some more details on this a little later this week - as a user of

cloudaws.Service

- we'd love your early feedback on this and whether it would address your needs.

Yes I may take a stab at a PR tomorrow as we need this flag asap. I would definitely be interested and happy to provide feedback on the ECS native API.

Run

make ensure

and then

make

in the root of the project. That will set up

yarn

links for all the packages built in this repo. From your test program, you can then run

yarn link @pulumi/cloud

and

yarn link @pulumi/cloud-aws

. I believe that currently to work with the dev process you do need to use

yarn

instead of

npm

(just due to the linking hooked up as part of the dev build process).

I see there's a #contribute channel. I'll move the conversation there.