Anyone have issues with lambda policy attachments getting removed by the automation API? We perhaps have a unique situation: a Pulumi project inside of our main Pulumi project that is deployed with the automation API. Its along the lines of this example: https://github.com/pulumi/automation-api-examples/tree/main/nodejs/localProgram-tsnode For some reason when the automation API deploys the child project, policy attachments associated with lambdas in the "main" project are removed. The pulumi stack still thinks those resources are there, and it takes a

pulumi refresh

and a

pulumi up

to reattach those policies.