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

image.png

Most of the company is on leave this week, so I'd suggest sticking to an old version of Pulumi if that works.
I'd suggest also raising an issue so this can be looked into when everyone's back next week.

thanks for the suggestion <@U02J3T6A8LB>, I tried going back all the way to 3.44.3 with no luck

I'd suggest raising an issue, I've not seen anything like this before. If you can run with debug logs "-v10 --logtostderr" and attach those to the ticket (or let us know on the ticket you've got them and we can give you an email address to post to), those logs would help a lot in working this out.

thanks again <@U02J3T6A8LB> - turning up the verbosity shed some light on what is happening, it looks like there is an issue with getting the log analytics workspace keys, its quite possible I may have this setup wrong, but still seems like a bug that the error didn't bubble up, I'll go ahead and file an issue