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

It’s not _currently_ possible but we’re trying to work out a way of doing this because it allows us to do circular dependencies

But as you say, it’s not very declarative which makes it hard

yeah the circular dependency was actually the reason i asked

i guess in my case i can create a resource called UpdateFunctionEnv which handles this right

it’s a bit… hacky… but if you can update the environment using the AWS CLI then we have the command provider for this: <https://www.pulumi.com/registry/packages/command/>

but it might be a workaround

i would basically just want to run the `UpdateFunctionConfiguration` aws-sdk v3 command

Yeah - the `Command` package is probably the best way to go for now.  That will ensure you can control the lifecycle of these additional actions as part of the CRUD lifecycle (unlike with `apply` which just runs on every update).

We would love in the future to allow something like Command but with callbacks you can implement directly in code (as callbacks invoked on Create/Update/Delete), so that you could just use the SDK directly instead of having an AWS CLI dependency.

There's some other discussion on future opportunities in this direction in <https://github.com/pulumi/pulumi/issues/3021>, <https://github.com/pulumi/pulumi/issues/13999> and <https://www.pulumi.com/blog/exploring-circular-dependencies/>.

gotcha makes sense i'll poke through those

giving some tools for circular deps would be major - one of our biggest places we have hacks in CDK

Command and a dynamic provider are roughly the same solution in this case right? i wanted to avoid spawning a new process