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

Is there any ETA on <https://github.com/pulumi/pulumi-yaml/issues/466|Issue 466: >`pulumi up`<https://github.com/pulumi/pulumi-yaml/issues/466| fails on update when using resource outputs as inputs to other resources>. I'm down across the board now for 2 days all envs dev/stage/prod.

Did you happen to notice this workaround? <https://github.com/pulumi/pulumi-docker/issues/685#issuecomment-1652473263>

Sharing in case it's helpful for your scenario while the team addresses the issue.

<@U041MGL883T> do you have any idea of what version this did work at?

I’ll add this to the ticket notes also, but the workaround isn’t applicable in my instance…. there’s two different resource types that were erroring on version 3.76.1 &amp; 3.75.0. Our last working update was on 3.76.0.

```type: gcp:cloudfunctions:Function
output: httpsTriggerUrl

type: gcp:vpcaccess:Connector
output: id```

Thanks for the information. We have marked this issue as a P1, meaning an engineer will get to it in their next available cycle.