Get error "Cannot bind argument to parameter 'Path' because it is null" using AWSPowerShellModuleScript@1 every now and then in Azure Devops pipeline

[khemebuen]

We are using Azure Devops and are running terraform which stores state files in S3. When we use AWSPowerShellModuleScript@1 every now and then we get the error "Cannot bind argument to parameter 'Path' because it is null". At times when we replay the stage it works but most of the time we replay and it still fails with same error.

Or yaml snippet is llike this

  - task: AWSPowerShellModuleScript@1
    displayName: "Terraform Plan"
    name: "terraformPlanTask"
    inputs:
      awsCredentials: '${{ parameters.awsCredentials }}'
      regionName: '${{ parameters.awsRegion }}'
      scriptType: 'inline'
      inlineScript: |
        terraform init -upgrade -backend-config="${{ parameters.backendConfigFile }}"

        terraform validate

We are running on Windows vms's hosted on Azure.

Here is a snppet of the error

[afroz429]

Is it possible to share the script AWSPowerShellModuleScript@1? It's not clear what command is failing.

[khemebuen]

This script is the Azure devops plug-in for AWS Powershell. The reason I posted here is maybe someone has ran into this issue. Maybe the script is on the the github repo. It fails for us during initialization of the AWSPowershellModuleScript v1. Sometimes it works and others it fails. We are not sure what conditions cause it to fail.

[amlynnworth]

Looks to me like the only piece that is a Path aka a File is this

parameters.backendConfigFile

which would make sense if your process occasionally passes in something invalid such as an empty string.

[khemebuen]

We figured out what the issue was. We see this when a job gets picked up by a machine that didn’t start the first job. It doesn’t have the source files needed hence the path not found error. We have fixed. Our build stages now pulls down the commits if they do not exists. We have not seen this Issue for the past couple of months now. Thanks Roland

…

On Saturday, August 17, 2024, Ann ***@***.***> wrote: Looks to me like the only piece that is a Path aka a File is this parameters.backendConfigFile which would make sense if your process occasionally passes in something invalid such as an empty string. — Reply to this email directly, view it on GitHub <#352 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFUYNMCY5KELJR3XB4NLAVLZR3YCXAVCNFSM6AAAAABI2UMDN2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZWGQ3TKNA> . You are receiving this because you authored the thread.Message ID: <aws/aws-tools-for-powershell/repo-discussions/352/comments/10364754@ github.com>