powerful-football-8169403/20/2020, 10:10 PM
task. Anything executing in the pipeline is able to implicitly authenticate to the package feed.
Except the Pulumi Task Extension for Azure DevOps. When the program is built by Pulumi, this authentication for some reason does not work. It is as if the normal environment variables, or some other ambient/contextual thing, are not visible to dotnet.exe when it’s called from Pulumi.
task, executing the command
also does now seem to be able to restore packages from this feed. We need to use the
(restore command) tasks to restore, before doing
task, the same error occurs during the latter.
clever-sunset-7658503/23/2020, 4:09 PM
of its own, it probably also tries to restore the NuGet deps again, which fails possibly due to the ambient context thing with authenticating to an internal package feed. Until I take a look, though, I am wondering if there is a way to disable Pulumi CLI from rebuilding the solution by passing some flags, @tall-librarian-49374?
tall-librarian-4937403/23/2020, 4:11 PM
powerful-football-8169403/23/2020, 4:11 PM
clever-sunset-7658503/23/2020, 4:13 PM
I believe there’s no way to disable the build currently…Is that worth adding as a feature? I can see how that might be useful in cases where you are only deploying from pre-built artifacts rather than rebuilding from source again.
powerful-football-8169403/23/2020, 4:14 PM
that would solve the issue too. Then I could pass
and work around this issue that way.
clever-sunset-7658503/23/2020, 4:17 PM
If there was a way to pass-through arguments toTo my knowledge, no. But @tall-librarian-49374 please correct me if I am wrong.that would solve the issue too.
tall-librarian-4937403/23/2020, 4:17 PM
powerful-football-8169403/23/2020, 4:18 PM
clever-sunset-7658503/23/2020, 5:51 PM