Database credentials incorrect

[rkoumans]

It seems that after the last update there is something wrong with updating the connection credentials. We use the option 'Azure SQL (single connection)'. The connectionstring isn't updated with the credentials proviced in the release pipeline. Instead of this the original credentials are deployed.

Can you look into this?

Regards, Ralph

[liprec]

Can you run the pipeline with an extra variable System.Debug and set it to true? And what kind of datasource connection is defined in the model.bim?

[rkoumans]

I added the extra variable. What info do you need from the logging? We defined a Azure Synapse database connection (SQL authentication)

[liprec]

Can you share the logs? You can alter server urls, usernames and so. Main reason is to see which code path is triggered.

[rkoumans]

Release_log.txt

[liprec]

Looks like your model definition doesn't have a name property (or it is an empty string) for your (first) datasource. The new version (due to the support for multiple datasources) searches for the datasource by name and cannot find the datasource (Applying datasouce credentials for ''). Can you validate if the name property exist in your bim file?

"dataSources": [
      {
        "type": "structured",
        "name": "WideWorldImporters",
...

[rkoumans]

The name property exists. See code below

"dataSources": [
  {
    "type": "structured",
    "name": "AzureSynapse",
    "connectionDetails": {
      "protocol": "tds",
      "address": {
        "server": "xxxxxxx.database.windows.net",
        "database": "xxxxxxx"
      },
      "authentication": null,
      "query": null
    },
    "credential": {
      "AuthenticationKind": "UsernamePassword",
      "kind": "SQL",
      "path": "xxxxxxx.database.windows.net;xxxxxxx",
      "Username": "xxxxxxx",
      "EncryptConnection": true
    }
  }

[liprec]

My bad, just realized that there is something going wrong with the default of the new dataSources option: it is not empty and used to replace the datasource credentials. Will provide a fix for this anytime soon.

What you can do for now is to migrate to the new 'Advanced' option and use the dataSources option instead of the 'Azure SQL (single connection)' details:

[
  {
    "name": "AzureSynapse",
    "authenticationKind": "UsernamePassword",
    "connectionDetails": {
      "address": {
        "server": "xxxxxxx.database.windows.net",
        "database": "xxxxxxx"
      }
    },
    "credential": {
      "Username": "xxxxxxx",
      'Password": "xxxxx",
    }
  }
]

[rkoumans]

Thanks for the update. We will wait for the fix and update the credentials in AAS ourselves.

[liprec]

The extension had been updated to version 1.5.3 and will be available anytime soon.

[rkoumans]

Just to let you know. The change worked. Thanks for the quick response.