search

Azure-Player / azure.datafactory.devops

Azure DevOps Deployment Tasks for Azure Data Factory objects
MIT License
39 stars 21 forks source link

##[error]Unable to deserialize the response. #59

Closed pjtaylor closed 2 years ago

pjtaylor commented 2 years ago

After yesterday's release, our deployments started failing with the below. Any thoughts?

STEP: Deleting objects not in source ... Azure Data Factory (instance) loaded. DataSets: 40 object(s) loaded. IntegrationRuntimes: 3 object(s) loaded. LinkedServices: 23 object(s) loaded.

[error]Unable to deserialize the response.

Finishing: PublishADFTask

NowinskiK commented 2 years ago

I need more information. Can you switch VERBOSE or DEBUG mode ON and show me part of the log? I need it to investigate WHERE exactly this could happen.

NowinskiK commented 2 years ago

Oh... wait... this is actually Deleting objects not in source stage, right? This might be related to one of the bugs in Az.DataFactory module. Can you run this command in PowerShell (having azure.datafactory.tools imported):

$ResourceGroupName = 'rg-devops-factory'
$DataFactoryName = "SQLPlayerDemo"
$adfIns = Get-AdfFromService -FactoryName "$DataFactoryName" -ResourceGroupName "$ResourceGroupName"
$adfIns.AllObjects()

This command will read all objects from ADF service as Deleting objects not in source stage does.

NJLangley commented 2 years ago

In case it helps, I had the exact same error message running he commands in PowerShell manually. a few weeks ago. One of the pipelines in the factory was invalid, and this causes the Az.DataFactory module to fail with that error when you try and list the files (same from .Net too). Solution was to remove the broken pipeline, and then the list function works again.

It seems the Az.DataFactory module does not validate the objects as well as it should as they are uploaded, but that then breaks the list functionality in the module.

pjtaylor commented 2 years ago

Thanks for your responses, guys. I've tried to reproduce the error with the latest 0.91 of the tools and can't so I assume this issue was related to one of the other bugs raised. Closed accordingly.