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?