This message was deleted.

sparse-intern-71089

06/16/2023, 9:47 AM

This message was deleted.

echoing-dinner-19531

06/16/2023, 10:07 AM

3.72.0 updated our go.cloud dependency (which we use for the azblob support), so I suspect this is probably actually a problem in go.cloud. Do you also have AZURE_STORAGE_ACCOUNT set?

worried-arm-83283

06/16/2023, 10:08 AM

yes I do have AZURE_STORAGE_ACCOUNT set

worried-arm-83283

06/16/2023, 10:08 AM

same env variables, older version login ok

echoing-dinner-19531

06/16/2023, 10:10 AM

Can you try 3.71? If that works it pretty much guarantees an issue with go.cloud but if you can check that and raise an issue at https://github.com/pulumi/pulumi/issues we can see if we can dig into what's changed with go.cloud to cause this.

worried-arm-83283

06/16/2023, 10:13 AM

3.71 works

echoing-dinner-19531

06/16/2023, 10:15 AM

Thanks almost certainly a go.cloud issue, I have a feeling we saw something similar last time we tried to update go.cloud I'll see if I can dig that up as well.

echoing-dinner-19531

06/16/2023, 10:17 AM

https://github.com/pulumi/pulumi/issues/11982 yeh there were azure issues when we tried to update to 0.28, I guess 0.29 still has those issues but we never managed to reproduce the problem to be able to raise an issue with go.cloud as to what was broken.

98 Views

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.