Jake Morrison

I believe I know what @nickadam is trying to convey. Given the following PowerShell Lambda code: ```powershell #Requires -Modules @{ModuleName='AWS.Tools.Common';ModuleVersion='4.1.32'} #Requires -Modules @{ModuleName='AWS.Tools.S3';ModuleVersion='4.1.32'} $ErrorActionPreference = 'Continue' # Amazon.S3.AmazonS3Exception: Access Denied...

From [ErrorAction:](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_commonparameters?view=powershell-7.2#-erroraction) - ```-ErrorAction:Continue``` displays the error message and continues executing the command. Continue is the default. - ```-ErrorAction:SilentlyContinue``` suppresses the error message and continues executing the command. I'm still...

@ashishdhingra Sure thing. Attached you can reference the full output log of the Publish command. [publish_awspowershelllambda_logs.txt](https://github.com/aws/aws-lambda-dotnet/files/8128143/publish_awspowershelllambda_logs.txt) The Lambda publishes to the AWS account without issue. It just errors on execution...

I wanted to add that I updated the Lambda deployment today to the new release of: [.NET 6 runtime for AWS Lambda](https://aws.amazon.com/blogs/compute/introducing-the-net-6-runtime-for-aws-lambda/) This issue *persists* with the same behavior with...

> May need to fix that so you can replace just the module or specific cmdlet placeholder text. @tnieto88 - I think that's exactly what's needed. Presently the new version...

For now, I've elected to address this via additional documentation. I recognize that overall, module dependency is something that could stand to be improved. I have not settled on something...

I'd love to see it support it as well. Unfortunately I don't have much experience with Octopus Deploy. I've tagged this as help wanted and will definitely be open to...

> If you test the individually and then build the module you aren't accurately testing the code that you're shipping, simple things like $script: or $global: variables may be set...

I have been able to reproduce this. Unfortunately, I have yet to figure out how to solve it. It seems that when ```Get-Item``` picks up the file it doesn't encode...

* One possible solution: http://wragg.io/add-a-code-coverage-badge-to-your-powershell-deployment-pipeline/ * [CodeCov](https://docs.codecov.io/docs/supported-languages) still has no PowerShell support * [Coveralls](https://docs.coveralls.io/) still has no PowerShell support