This message was deleted.

sparse-intern-71089

05/31/2021, 3:15 AM

This message was deleted.

little-cartoon-10569

05/31/2021, 3:18 AM

You'll need to do this.

curved-pharmacist-41509

05/31/2021, 3:19 AM

Great, thanks for confirming

👍 1

curved-pharmacist-41509

05/31/2021, 3:19 AM

This would be awesome to have an implicit dependency here. It prevents a component resource creating the execution role, then attaching additional resource policies to that execution policy outside of the component resource

little-cartoon-10569

05/31/2021, 3:23 AM

Yes, though the explicit dependency is good for self-documentation purposes. And would there be cases where Pulumi would guess incorrectly? For example, if there were multiple RolePolicyAttachments and only one was relevant to the lambda?

curved-pharmacist-41509

05/31/2021, 3:54 AM

Possible. Thoughts on this pattern?

Copy code

const executionRole = new LambdaExecutionRole()

new Lambda('', { role: executionRole.role }, { dependsOn: [executionRole] }))

executionRole.attachPolicy(...)

This would create a role policy attachment with parent of the LambdaExecutionRole. Allowing role policy attachments to be added after the lambda has been `new`ed up, but also creating a dependency between the RPA’s and hte lambda?

Open in Slack

Previous Next

Pulumi Community

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.