Echo Dotnet Publish

[tmakin]

Issue
I had an issue with lambda deployment caused by the failure of dotnet publish. However, I was unable to replicate the problem by calling dotnet publish manually. In order to debug the issue, I added an additional log statement to output the publish args being used internally by the lambda tool. In my case, it was nuget package resolution issues that only showed when the --runtime linux-x64 arg was used.

I think my change would be a useful addition for others in order to help debug publish failures.

Changes

• Added additional log statement to LambdaDotNetCLIWrapper.Publish

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[tmakin]

Hi team, is there any way I can see the build error so I can fix the PR?

[normj]

Thanks for the PR. I merged it into the dev branch to go out with the next release. Don't worry about the CodeBuild failure, I need to get that removed from GitHub as the CodeBuild job isn't used or exist anymore.

[tmakin]

Thanks @normj. I originally included some suggestions for the contributing guide in the PR, but I removed when I was trying to get rid of the CodeBuild error. Please have a read of my notes here, and if you think it would help others then I'll submit another PR:
https://github.com/tmakin/aws-extensions-for-dotnet-cli/blob/contributing-update/CONTRIBUTING.md#local-tool-development

[normj]

I like the local tool development section. I would accept that as a PR.

[normj]

Version 4.1.0 of Amazon.Lambda.Tools went out today with this PR. Thanks!