Fraser Waters

Found a repro. It was a combination of "--refresh", "--targets", a provider upgrade, and one resource being removed from the program at once. Will look at at least fixing this...

I suspect this is a problem with lists vs sets. Probably the aws provider diff method that's not handling this quite right. Moving repos.

He @matanbaruch sorry I think this got dropped, I did a first review a while back and pinged it up to @lunaris and management to ok, and they had said...

``` Command: pulumi state delete urn:pulumi:sandbox::infra::azure-native:containerinstance:ContainerGroup::openfgaseed-container-group --force ``` I'm assuming the initial command that caused an issue was _not_ `pulumi state delete`. Can you share what update initially triggered an...

Circular dependencies are _hard_. We wrote a blog post about it couple of years ago https://www.pulumi.com/blog/exploring-circular-dependencies/. We'd love to find a way to support this in a first class manner,...

> Am I understanding correctly that Pulumi doesn't respect PYTHONPATH when resolving packages? No this is just how python module resolution works. I would not expect the repo shown in...

Thinking about this for a bit I'm inclined to say we probably shouldn't do option 1 above. Users can easily already set that themselves via the envvar which also gives...

> I could be mistaken but I don't think this is accomplished by the PR. We already have a project option for changing the root directory the runtime starts in...

Yes that's standard python behaviour

> it would be nice to not have to specify the module path in this scenario where the layout is actually default/trivial. It would, but I think that would be...