Config file format change?

[BigTP25]

I have csv config files for each environment for our data factories (Dev, UAT, STG, Prod). I am following the format type, name, path, value like the documentation states. I have not change the entries in the config files for months...and all of a sudden I am getting this error [error]ADFT0010: Wrong path defined in config for object(path): linkedService.Nexus(properties.typeProperties.connectionString)_

Any ideas if anything changed? Or what I need to do to get this working again?

[BigTP25]

Any help would be greatly appreciated. The workaround, for now, is to go into this linked service and manually change the connection string for the server it needs to connect. It would be ideal to have this changed during deployments via the config file but I am stuck ATM with this error. Removing these entries in the config file results in successful deployments but, like I said, these entries in the config files haven't changed.

[BigTP25]

I took out the entry to specify the URL for SQL Server and just kept the entry to set the default name for the database and I get the same error. I am really struggling right now...I don't know what else to check. The error seems to indicate a problem with the entries in the config file but they seem fine. The deployments work fine if I set the pipeline task to use the stage option vs stating the location of the config file.

[BigTP25]

@NowinskiK I have figure out the issue and its pretty crazy...

The JSON for the linked service is different between two data factories...
This is the JSON for the linked service where I was having problems deploying

This is the JSON for the linked service in another ADF for a database on the same logical server...

The linked service in both ADFs is an Azure SQL Database but as you can see the JSON behind them is different in two different ADFs. This is why is was throwing the error it was because the properties changed in the JSON.

As usual...thank you for being so responsive!!!

[NowinskiK]

But... is it the same object (Linked Service)? Which version do you have in your code repository?
The deployment should take ADF & config files from the same folder (location), so that config entries represent correct ADF's objects.
It doesn't matter what is in the target ADF. The deployment works with ADF files from the repo - that should be your source of truth.

[BigTP25]

@NowinskiK It's the same object type, Azure SQL Database. Two separate ADFs, same linked service type, different JSON structure. The top one is the "new" JSON structure where as the bottom is "old". Basically, the connectionString property doesn't exist anymore for Azure SQL Databases and the connection string has been broken out into separate property elements in the "new" JSON.

[NowinskiK]

This means someone has changed the definition of nexus Linked Service - switched from "legacy" (ConnectionString) to "Recommended" (new) on DEV environment / repo:

For record purposes - differences:

Legacy (ConnectionString)

{
    "name": "LS_AzureSqlDb",
    "properties": {
        "annotations": [],
        "type": "AzureSqlDatabase",
        "typeProperties": {
            "connectionString": "Integrated Security=False;Encrypt=True;Connection Timeout=30;Data Source=sqlplayer.database.windows.net;Initial Catalog=master;User ID=sql",
            "password": {
                "type": "AzureKeyVaultSecret",
                "store": {
                    "referenceName": "LS_AzureKeyVault",
                    "type": "LinkedServiceReference"
                },
                "secretName": "sqlserver-sql-password"
            }
        }
    }
}

Recommended (new)

{
    "name": "LS_AzureSqlDb",
    "properties": {
        "annotations": [],
        "type": "AzureSqlDatabase",
        "typeProperties": {
            "server": "sqlplayer.database.windows.net",
            "database": "master",
            "encrypt": "mandatory",
            "trustServerCertificate": false,
            "authenticationType": "SQL",
            "userName": "sql",
            "password": {
                "type": "AzureKeyVaultSecret",
                "store": {
                    "referenceName": "LS_AzureKeyVault",
                    "type": "LinkedServiceReference"
                },
                "secretName": "sqlserver-sql-password"
            }
        }
    }
}