No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Is it on purpose that `ResourceRequirements` has the type as `pulumi.Input&lt;object&gt;` instead of having a named object with `cpu` and `memory`?

Which `ResourceRequirements` is this? For ECS at least - I don't see `Input&lt;object&gt;`?  Is this in Kubernetes?

<https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/aws/ecs/#ResourceRequirements>

<@UGDSK5RNC> I think its because of <https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#extended-resources>

if you check the example on the bottom, `limits` and `requests` can have custom keyvals

And there’s no way to support both with typing?

There is, but the types are autogenerated from the openapi spec if I recall correctly

so if its getting created as just an object then the openapi spec must define it like that

Because it’s a bit of a bad experience when working with an IDE. Autocompletion isn’t there because of this.

Yeah - that makes sense.  I've actually noticed this with a few Kubernetes properties.  Mind opening an issue?  I think it's likely we could improve this at least in TypeScript.

<https://github.com/pulumi/pulumi-kubernetes/issues/843>