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

Thanks for asking, I’ve been wondering that too. :heavy_plus_sign:

Either approach is valid, and comes down to preference.    Often I see longer, more complex, or pre-defined policies defined in .json or .yaml files and loaded, while short or programmatically generated IAM policies are defined in-line with code (using  multi-line strings)

additionally, in python, it can be quite convenient to define a policy as an object (dict), and render it into json with `json.dumps(policy_obj)`

No, no preference, :laughing: . That’s too difficult to have code uniformity :laughing: :wink:

I hate the fact that for myself, I keep flip flopping thinking doing one way and then I feel like another way is better.

I typically do it inline myself, if that helps...  feels weird to load code into a program from a file, when i can just have it part of the program (since json is just code)

Yes, it’s just that sometimes it makes “the code” longer… Yep just preference and convenience …