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

You’re approach is valid and is the proper decoupling with regards to how you’re splitting your stacks.

I can see an argument for the user to provide this entire `roleMappings` config block, but `pulumi/eks` would also need the user to pass in the `instanceRole` mapping in the `roleMappings` as well, as it currently handles that: <https://github.com/pulumi/pulumi-eks/blob/master/nodejs/eks/cluster.ts#L268-L323> - specifically Line 315.

If this `roleMappings` is supplied, I believe `pulumi/eks` would at best load it to parse and validate that its valid YAML, as trying to validate anything further like if users and roles are properly configured in it, can be a bit of a guessing game. This would put the onus on the user to make sure it is complete and correct.

thanks Mike - sorry for the slow feedback