Publish GlobalParams fail when globalConfigurations exist but Global Params list is empty

[ederfdias]

I am trying to run a pipeline like this:

• task: SQLPlayer.DataFactoryTools.PublishADF.PublishADFTask@1 displayName: 'publish to ${{ parameters.dataFactoryName }} adf in env ${{ parameters.branch }}' inputs: azureSubscription: ${{ parameters.azureServiceConnection }} ResourceGroupName: ${{ parameters.resourceGroupName }} DataFactoryName: ${{ parameters.dataFactoryName }} DataFactoryCodePath: '$(System.DefaultWorkingDirectory)/dataFactory' Location: ${{ parameters.location }} StageType: FilePath StageConfigFile: '$(System.DefaultWorkingDirectory)/dataOps/configs/${{ parameters.branch }}.csv' DeleteNotInSource: true CreateNewInstance: false PublishMethod: 'AzResource' IgnoreLackOfReferencedObject: true TriggerStartMethod: KeepPreviousState

It was running fine some days ago, but now start to stop with the error below:

Adding global parameter...

[error]You cannot call a method on a null-valued expression.

I double check permission, variables, etc. The only thing was changed is that we create a new Data Factory resource.

One interest thing is even reporting an error the o check ADF in live mode and the pipelines is deployed.

Any guess?

[NowinskiK]

Hi. Can you provide more details from the log after enabling "System Diagnostics"?

[ederfdias]

2024-02-05T130335.0319116Z.txt Hi Nowinskik, log attached.

[BigSlimeGuy]

Hi NowinskiK, Our team recently started using this great DevOps plugin and we encountered the same issue. As a workaround we added a global parameter, which resolved the error.

[NowinskiK]

@BigSlimeGuy can you show me your factory file? I'm wondering what's special about this file that the process fails... it works for most people.

[ederfdias]

Looks like to me it's some update on data factory side

[ederfdias]

I have some old factories that works nice with the same task, but when I create a new adf the issue start to happen

[ederfdias]

@BigSlimeGuy can you show me your factory file? I'm wondering what's special about this file that the process fails... it works for most people.

Which file do you want to see specifically? Any specific json or the arm file generated?

[BigSlimeGuy]

@NowinskiK the factory that failed with the null reference exception looks like this:

{
    "name": "dev-weu-int-adf",
    "properties": {
        "globalConfigurations": {
            "PipelineBillingEnabled": "true"
        }
    },
    "location": "westeurope"
}

Then when we added a global parameter, the null reference went away:

{
    "name": "dev-weu-int-adf",
    "properties": {
        "globalParameters": {
            "test": {
                "type": "string",
                "value": "test"
            }
        },
        "globalConfigurations": {
            "PipelineBillingEnabled": "true"
        }
    },
    "location": "westeurope"
}

Not sure if this is relevant, but we deploy the ADF instance using bicep. So it is completely clean, perhaps if you create it via the portal it will contain the globalParameters field with an empty object or something?

[NowinskiK]

Thanks for more details, I will check that out.

[ederfdias]

Thank you all

[ederfdias]

@NowinskiK do you know if there plan to apply the same solution here in this repo below? https://github.com/Azure-Player/azure.datafactory.devops

I just noted that we have installed that extension from marketplace: https://marketplace.visualstudio.com/items?itemName=SQLPlayer.DataFactoryTools

I think it uses this tools somehow.

[NowinskiK]

Yes, this PowerShell module is fully used by DevOps Extension. Somehow I missed updating to v1.9. I will do that tonight.

[NowinskiK]

Released: https://github.com/Azure-Player/azure.datafactory.devops/releases/tag/v1.33 Version: 1.33.1471 (marketplace)