ADF Global Parameters validation failed using NPM Run validate command

Question

Below CICD YAML deployment code is getting failed "customCommand: 'run build validate $(Build.Repository.LocalPath) /subscriptions........" is getting failed due to usage of global parameters in various pipelines."with below error2024-02-29T14:01:25.5226531Z  Validator: Error for Expression: '@pipeline().globalParameters.ENV', Expression Error Message: 'Parameter ENV was not found under adfdevnew', attribute: '{"name":"value","display":"Set variable","templatable":true,"_owner":{"name":"SetVariable","display":["Set variable activity","Set variable activities"]}}', obj: '{"_object":{},"_owned":{},"_ancestor":{},"_model":{},"_aObject":{}}', resolution: '{"kind":0,"details":{}}', resolution.error: '{"kind":0,"details":{}}'In ADF activity, we are just setting a set variable with below dynamic query builder@concat('https://management.azure.com/subscriptions/',pipeline().globalParameters.SubscriptionID,'/resourceGroups/',pipeline().globalParameters.ACG_ResourceGroup,'/providers/Microsoft.ContainerInstance/containerGroups/',pipeline().globalParameters.ACG_Name)

Any solution will be appreciated.

Answer 1

@JyotiranjanMangaraj-6157 In this case, the issue might be related to the way the global parameters are being deployed to ADF. When you create global parameters using Terraform, they might not be immediately available for use in the pipeline.
To resolve this issue, you can try the following:

1. Verify that the Terraform script is successfully deploying the global parameters to ADF.
2. Check the Azure Data Factory REST API to ensure that the global parameters are available. You can use the GET /globalParameters API to retrieve the list of global parameters.
3. Try running the NPM command with the --debug flag to get more detailed error messages. This might help you identify the root cause of the issue.
4. If you're using Azure DevOps, ensure that the ADF pipeline is properly linked to the Azure subscription and resource group.

If none of these steps resolve the issue, please raise a support ticket for a deeper investigation.

I hope this helps. Please Let me know if you have any further questions.