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

How would one go about importing a kubernetes:yaml:ConfigFile as all the resources are dependents?

Yes - we do not have any story today for importing a component resource. (In some sense that doesn’t even make sense - there is no actual “thing” representing the component - so nothing to import directly). 

But the use case definitely makes sense - so it’s something we should figure out how to support in some way.  It’s possible that I’m this case - just having the component set `import` on all its children if set on itself would actually work? 

If there isn’t already one - could you open an issue to track this?