This message was deleted.

sparse-intern-71089

12/10/2019, 2:12 AM

This message was deleted.

fresh-flag-12765

12/10/2019, 2:13 AM

We had: • Merrily working CI • Added skip preview since the CI does preview anyway • CI skipped doing preview since it didnt detect any changes • Up failed • Now it assert panics on everything (preview/up/refresh) and somehow 37 resources are missing the

id

field

fresh-flag-12765

12/10/2019, 2:16 AM

Ah actually that maybe makes sense for most of them, if they're awsx

white-balloon-205

12/10/2019, 2:26 AM

Definitely not expected that any form of

up

would lead to asserts. I suspect this issue is unrelated to the change to add

skip-preview

. Could you open an issue with details of the panic?

fresh-flag-12765

12/10/2019, 3:47 AM

https://github.com/pulumi/pulumi/issues/3626 Let me know if theres any other details I can add

white-balloon-205

12/10/2019, 3:59 AM

Thanks - this looks like enough to investigate. That particular outcome is very surprising indeed. We’ll look into it.

fresh-flag-12765

12/10/2019, 3:59 AM

Also, I accidentally reproduced it by running the same CI again. Happened again.

white-balloon-205

12/10/2019, 4:02 AM

Good to know it’s a reliable repro I suppose - if you could note that in the issue that might help diagnosing. Sorry for the trouble - but sounds like you have a mitigation for this (though cumbersome)?

fresh-flag-12765

12/10/2019, 4:15 AM

No worries. Mostly just a pain to track down the cause. Added the issue to say that removing the

--skip-preview

did get things working again (after applying the mitigation).

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.