Thomas Gummerer

I think a new major release and changing the refresh functionality would make sense here as well. I think updating this PR sounds good, but no strong preferences here either...

I'd be happy to land this PR if @fitz-vivodyne wants to update it with the updated `refresh` functionality. Once that's done I can approve, merge and create a new release...

I just merged the changes to no longer display the `updateInProgress` field in the json output if we are using filestate backends, so I think we can consider the bug...

I'm gonna go ahead and close this issue out. Since it just gets continuously updated we've been ignoring it completely. These tests are still flaky, so we could potentially consider...

We implemented a `--continue-on-error` flag for `pulumi destroy` in https://github.com/pulumi/pulumi/pull/15727. This was released in pulumi 3.112.0. That flag does everything that's planned here minus this sidenote: > It's possible this...

I think this is basically ready now, but it includes the changes from https://github.com/pulumi/pulumi/pull/15504, since it depends on those for introducing the conformance test, so I'm leaving this in draft...

This looks similar to https://github.com/pulumi/pulumi/issues/14300.

Looking into this, there's a few things happening in this issue that are getting a little conflated. > Alarmingly, it looks like the merge workflow failed for this PR due...

/run-acceptance-tests Please view the results of the acceptance tests [Here](https://github.com/pulumi/pulumi/actions/runs/7179330647)

/run-acceptance-tests Please view the results of the acceptance tests [Here](https://github.com/pulumi/pulumi/actions/runs/7180251497)