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

Hey all!  I have a questions related to the golang AWS SDK.  Why do all of the Pulumi SDK APIs return inputs/outputs instead of primitive values?  I don't fully understand the architectural decisions around why Pulumi uses Inputs/Outputs with Apply/Lift methods.  This adds a lot of boilerplate and complexity to access the underlying raw value.  As I understand it, it's because Pulumi runs the code before actually making AWS API calls?  Can someone help me understand this?

This might help: <https://www.leebriggs.co.uk/blog/2021/05/09/pulumi-apply.html|https://www.leebriggs.co.uk/blog/2021/05/09/pulumi-apply.html>

I see, what I just realized is that creating a resource synchronously and getting the ID may not be possible, since the API may be a submit/poll-for-updates type of pattern