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

found exportStack but it not really clear where to remove them

```    try {
      const exportedStack = await stack.exportStack();
      if (exportedStack.deployment.pending_operations?.length &gt; 0) {
        exportedStack.deployment.pending_operations = [];
        await stack.importStack(exportedStack);
      }
    } catch (error) {
      // swallow
    }```

I think just the following should suffice because import doesn't import pending operations
```const exportedStack = await stack.exportStack();
await stack.importStack(exportedStack);```


that is different behaviour then from the CLI ? I clean them out with jq in CLI programs

<@U01038HJ93R> thanks for explaining that pending operations are auto omitted. I have in my automation pipeline similar code to <@U01BRSYUUDP>. Always glad to learn more about the code I’m calling :laughing:

I think <@U01BRSYUUDP> is right here actually, I was mistaken. Although I guess checking if there are pending operations isn't really necessary so you can save one line and do:
```const exportedStack = await stack.exportStack();
exportedStack.deployment.pending_operations = [];
await stack.importStack(exportedStack);```

<@U01038HJ93R> I think <@U01BRSYUUDP>’s code saves time, because it doesn’t import the stack if there aren’t any pending ops