3GDXC

I'm using AzureDevOps with the default Azure Agent Pool, image of ubuntu 16.04; I have added the AWS for DevOps tooling via the market place on the organizations account.

If required I'm able to provide the full logs of the build/publish; however these are large.

this may be linked to issue #316

FYI, here is a more complete log output ``` 2020-03-31T02:26:14.6646955Z ##[section]Starting: deploy .net core to lambda: 2020-03-31T02:26:14.6676720Z ============================================================================== 2020-03-31T02:26:14.6677079Z Task : AWS Lambda .NET Core 2020-03-31T02:26:14.6677624Z Description : Builds, packages...

more info; I created a task that deletes the nuget.config after the build/publish but prior to the Lambda task; the follow is the output of the log ``` 2020-03-31T02:49:06.2457368Z ##[section]Starting:...

could this be the root issue ? [command]/usr/bin/dotnet tool install -g Amazon.Lambda.Tools **Since you just installed the .NET Core SDK, you will need to logout or restart your session before...

@hunterwerlla yes, I would agree the **second** part of this issue around not finding the installed global tools looks to be a common **AzureDevOps** issue; the however the bug with...

@hunterwerlla https://github.com/dotnet/sdk/issues/9777 seems to suggest using the -tool-path switch do you know of this?

any update on this; I believe I'm also running into this same issue #336 I've included logs and have a step which deletes the nuget.config just prior the the lambda...

@ScottKane good work builds and updating locally every is fixed