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

having a lot of trouble importing existing lambda resources into pulumi, including errors for missing fields that are clearly defined on the existing resource in aws. this seems super buggy. does anyone have suggestions for working around this?

we'd love to get github issues for these use cases so we can triage/fix - sorry for the poor experience

okay! will definitely file issues if that's not annoying :slightly_smiling_face:

not at all, we definitely want to get import issues fixed!

<https://github.com/pulumi/pulumi/issues/7884>

also <@UCWG26BH7>, is the sort of thing that y'all would accept PRs for / i would be able to dig into? this is a blocker for our pulumi adoption (which we are overall extremely in favor of) and i'm not opposed to digging deeper into internals as a learning exercise as long as it wouldn't be an XL kind of project

yes we'd asolutely take a PR for this, thank you so much

let me try find somewhere we've previously fixed this

it looks like we have a few open issues related to lambda imports :disappointed:
<https://github.com/pulumi/pulumi-aws/issues/1379>

okay, well let me dig in and at least see what i can find :slightly_smiling_face: always happy to contribute back if possilbe

i'm more concerned about the event source mapping as that's the stateful bit here, we don't want to lose kinesis offsets

looks like the existing problem is being tracked, i was able to write a small patch that allows me to import resources, in the event any one else runs into this in the future, this may work for them as well <https://github.com/pulumi/pulumi/issues/7160>