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

Not dumb! Inputs and Outputs are a little tricky at first!

There's some string helper methods in the `pulumi` namespace that can help for stuff like IAM policies. What language are you using?

i can only imagine the pain of supporting several languages in pulumi

now to decide how to share data with circleci, that's going to be fun :smile:

Let me know how this page works for you: <https://www.pulumi.com/docs/using-pulumi/continuous-delivery/circleci/>

thanks for the link, actually it's an inversion of that, i want executions of pulumi to update my circleci projects with environment variables &amp; so on

i'm thinking for now the best thing to do is to create a role with credentials &amp; an SSM or aws secrets secret arn &amp; copy those into circleci by hand, it's only 3 bits of data so it's manageable. From there a CCI job can pull the secret/parameter &amp; hydrate the build environment

This should also be helpful with your earlier issue: <https://www.pulumi.com/docs/concepts/inputs-outputs/#converting-outputs-to-json>

If you're using the Pulumi Cloud backend, you could use webhooks to do stuff after an execution completes. If not, try the Automation API - it lets you embed Pulumi in other programs.

yeah actually i was meaning to ask someone about that; it seems that the automation api still requires the pulumi binary to be available right?

i presume that has to do with executing go code?

I... don't know. It might, but if it does, I'm guessing it will be installed when you `npm i`, just like the provider binary is installed when you `npm i @pulumi/aws`.

right, ofcourse go gets compiled to a binary doesn't it

The multi-language support in Pulumi is possible because providers are binaries with gRPC interfaces. The SDKs just proxy gRPC calls to a known binary, more or less.