/
AWS Lambda Environment Variables Accepted Structure

AWS Lambda Environment Variables Accepted Structure

File Format Acceptable Structure

These are the accepted file formats for the environment variables.

Supported Format 1 (JSON)

[{ "keyName": "Mysql_Connection_String", "secured": false, "keyValue": "jdbc:sqlserver://localhost;databaseName=DbName;user=MyUserName;password=*****;" }, { "keyName": "Queue_Conn_String", "secured": true, "keyValue": "DefaultEndpointsProtocol=https;AccountName=storageaccnt2508;AccountKey=z4zvWOWMVweXrD6vhUeFQh8I+AStPzq/9w==;EndpointSuffix=core.windows.net" }]

Supported Format 2 (CSV)

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

 

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:

[{   "keyName": "Mysql_Connection_String",    "secured": "false",    "keyValue": "jdbc:sqlserver://${{SQL_DB_ENVWISE_HOST}};databaseName=DbName;user=MyUserName;password=*****;" }, {   "keyName": "Queue_Conn_String",    "secured": "true",     "keyValue": "DefaultEndpointsProtocol=https;AccountName=${{Storage_Account_Name}};AccountKey=z4zvWOWMVweXrD6vhUeFQh8I+AStPzq/9w==;EndpointSuffix=core.windows.net" }]

 CSV Format:

Input Argument Acceptable Structure

Any entry to environment variables as workflow input would work in upsert mode. They will be added along with the entries present as part of the environment variables 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.

Below are given Input argument formats for the environment variables.

Supported Format 1 (JSON)

Supported Format 2 (CSV)

 

Related content

AWS Lambda Function Add Environment Variables
AWS Lambda Function Add Environment Variables
More like this
AWS Lambda Function Code Deploy Using S3 with Blue Green Deployment
AWS Lambda Function Code Deploy Using S3 with Blue Green Deployment
Read with this
AWS Lambda Environment Variables Accepted Structure
AWS Lambda Environment Variables Accepted Structure
More like this
upsertFunctionConnectionString
upsertFunctionConnectionString
Read with this
AWS Lambda Function Add Environment Variables
AWS Lambda Function Add Environment Variables
More like this
upsertFunctionApplicationSetting
upsertFunctionApplicationSetting
Read with this
The following macros are not currently supported in the footer:
  • style