This message was deleted.
# azures
sparse-intern-71089
11/08/2020, 12:19 AMThis message was deleted.
w
wet-noon-14291
11/08/2020, 12:20 AMto make it even more interesting. It works on my machine but not on azure devops :)
b
broad-dog-22463
11/08/2020, 1:49 PMThis is C# right @wet-noon-14291 ?
w
wet-noon-14291
11/08/2020, 1:59 PMYeah. Or F#... but .net sdk.
b
broad-dog-22463
11/08/2020, 2:11 PMI believe I’ve identified the commit that has changed this
broad-dog-22463
11/08/2020, 2:12 PMI’ve posted in an internal channel about this
broad-dog-22463
11/08/2020, 2:12 PMSorry!!
broad-dog-22463
11/08/2020, 2:12 PMCan you open an issue that we can reference so others can see it?
t
tall-librarian-49374
11/08/2020, 8:51 PMThis is likely because you are using Pulumi (CLI) pre-2.13.0. There was a change in Pulumi.AzureNextGen discovery that only works with the latest CLI.
w
wet-noon-14291
11/08/2020, 10:37 PMI think I know why I sort of experienced this, and based on your comment @tall-librarian-49374 I don't think it is pulumi's fault. When I started using pulumi I don't think pulumi was available as a pre-installed tool for the AzureCLI task, but it seems like it is now. I might been wrong on this though. The version installed is 2.12.1. So when I installed pulumi manually and added pulumi to the path I added it after the pre-installed one so 2.12.1 was always used in the following tasks. Adding it to the beginning of the PATH env variable solved it.
wet-noon-14291
11/08/2020, 10:59 PMDoes anyone of you know where the default version of pulumi for the azure cli task is defined?
39 Views