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

Hi <@U015UJE4KV1>

This looks to be a similar issue to <https://github.com/pulumi/pulumi-azure/issues/601>

yeah same issue, only my pulumi project is dotnet and its run on an ubuntu-20.04x64 agent

Any ideas apart from manually installing pulumi sdk etc on agent?

<@UCWG26BH7> this is what you were investigating right?

i hadn't looked at it just yet, but I'll prioritize it today
<https://github.com/pulumi/pulumi-azure/issues/605>

they both feel a similar issue... :confused:

I have following:

W2.Portal.Infrastructure (the main pulumi project, references W2.Pulumi.Azure)
W2 Pulumi.Azure (Custom resources for azure)

I have tried adding a direct reference to the Pulumi.Azure nuget package from the main pulumi project also, but this did not make a difference

I have noticed that there is a version.txt file that is added to the projects that reference Pulumi.Azure. Is this what is used to detect the plugin versions?

I'm not entirely sure. You can workaround this by doing `pulumi plugin install resource azure v3.9.3` to acquire the binary plugin

This seems to only be an issue on ubuntu 20.04x64

I have switched to 16.04x64 and working, also working on windows x64

ok <@UCWG26BH7> I wonder if that is the same for the other issue...

<@UCWG26BH7> <@UHTP242EB> I am now experiencing this issue on windows agents also.

I have 2 releases, both for the same commit, first one deployed as expected, second had the previous issue of not being able to install azure provider plugin

<@UCWG26BH7> <@UHTP242EB> Here are the releases