This message was deleted.

sparse-intern-71089

06/05/2019, 4:57 PM

This message was deleted.

white-balloon-205

06/05/2019, 4:58 PM

What Pulumi cli version were you running? You should be able to

Pulumi cancel

to address the second issue. But would love to understand what caused the first.

cool-egg-852

06/05/2019, 5:01 PM

0.17.15

white-balloon-205

06/05/2019, 5:05 PM

If you are still seeing this after cancel - you could try downgrading to 0.17.14 as a workaround. I opened https://github.com/pulumi/pulumi/issues/2804 to investigate the assert.

cool-egg-852

06/05/2019, 5:06 PM

I’m trying it on a different stack (same project) right now. I’m curious to see if it fails as well.

cool-egg-852

06/05/2019, 6:04 PM

The issue didn’t happen on the stack. So we shall see as I have 4 stacks to go through in total, and I’ll circle back to the one that had an issue.

bitter-oil-46081

06/06/2019, 12:19 AM

FWIW, @cool-egg-852 We pushed a change that we believe should address the issue. You can install a dev version of the CLI with the following gesture:

curl <https://get.pulumi.com/> | bash -s -- --version 0.17.16-dev.1559777246

But we plan to release a 0.17.16 shortly with the fix. Would be great to know if that ends up addressing your issue.

cool-egg-852

06/06/2019, 12:29 AM

I was never able to reproduce it so I can’t really test.

bitter-oil-46081

06/06/2019, 5:34 PM

I was never able to reproduce it so I can’t really test.

Okay, thanks.

Open in Slack

Previous Next

Pulumi Community

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.