Application Setting/Connection String file & input content acceptable structure

File format acceptable structure

Application Setting

Below is given file format of the Application Setting.

{
  "IsEncrypted": false,
  "Values": {
    "FUNCTIONS_WORKER_RUNTIME": "node",
    "AzureWebJobsStorage": "UseDevelopmentStorage=true",
	"SB_CONNECTION_STRING" :"Endpoint=sb://testsvcbus0209.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=MQN1lKTPtKsG+o+yFP1PTY6LAVuxKH5QvYLtpzcDifY="
  }
}

While creating the Azure function by default local.settings.json file is created. This file contains application setting values in the key: value pair sample file content shown below.

This file(or any other file name in the same format) can be used as an argument. In case of a missing file, it will just ignore it. All entries inside will be upserted in the Azure function.

Connection String

Any file with content aligned with the below-mentioned formats(JSON/CSV) can be used for the Connection String file.

Supported format 1 (JSON format):

[{   "paramName": "Mysql_Connection_String",
   "type": "mysql",
   "paramValue": "jdbc:sqlserver://localhost;databaseName=DbName;user=MyUserName;password=*****;"
},
{   "paramName": "AzQueue_Conn_String",
   "type": "custom",
    "paramValue": "DefaultEndpointsProtocol=https;AccountName=storageaccnt2508;AccountKey=z4zvWOWMVweXrD6vhUeFQh8I+AStPzq/9w==;EndpointSuffix=core.windows.net"

}]

Supported format 2 (CSV Format):

"Mysql_Connection_String": "mysql##jdbc:sqlserver://localhost;databaseName=DbName;user=MyUserName;password=*****;" , "AzQueue_Conn_String":"custom## DefaultEndpointsProtocol=https;AccountName=storageaccnt2508;AccountKey=z4zvWOWMVweXrD6vhUeFQh8I+AStPzq/9w==;EndpointSuffix=core.windows.net"

n.b. In the case of CSV payload, the type & parameter Value should be appended together with “##” separated.

Important note: Either entire or part of parameter value can be dynamic in nature (e.g. url, hostname, db name/port etc). In such cases the value can be stored in as Project /Environment properties and the placeholder can be added in file as shown below. In case the values are provided the placeholder would be replaced with actual value during deployment. The same implementation will be applicable while passing the input through input as well.

JSON format:

CSV Format:

Input argument acceptable structure

Any entry to Application Setting or Connection String as workflow input would work in upsert mode. They will be added along with the entries present as part of the Application Setting File/Connection Setting File. However, in case of the same value present in both, an entry made through input argument will take precedence over any value in the case provided through files in Project properties.

Application Setting

Input (JSON format):

Providing content directly as JSON or CSV is also acceptable.

Input (csv Format):

Connection String

Below are given modes through which Connection String values can be provided.

Input (JSON format):

Input (csv Format):