Provide the steps required to reproduce the problem:
I am using the Service Bus trigger for my application.
To load the Service Bus trigger connection string, currently, we rely on the Docker environment variable, which is dynamically set when the Azure pipeline is triggered
The Service bus trigger connection string should be successfully loaded from Azure Key vault upon function app startup
Actual behavior
Provide a description of the actual behavior observed.
Known workarounds
Provide a description of any known workarounds.
Currently, the connection parameter refers to any variable that holds the connection string. Hence we are hardcoding it as a Docker environment variable
The other alternative is to set it as a Kubernetes environment variable through Azure pipelines
However we want to fetch it from Keyvault
Contents of the requirements.txt file:
Provide the requirements.txt file to help us find out module related issues.
Investigative information
Please provide the following:
Repro steps
Provide the steps required to reproduce the problem:
I am using the Service Bus trigger for my application. To load the Service Bus trigger connection string, currently, we rely on the Docker environment variable, which is dynamically set when the Azure pipeline is triggered
Code
The
ServiceBusConnectionString
is referred as aDocker environment variable
in the Dockerfile as below:Expected behavior
Provide a description of the expected behavior.
The Service bus trigger connection string should be successfully loaded from Azure Key vault upon function app startup
Actual behavior
Provide a description of the actual behavior observed.
Known workarounds
Provide a description of any known workarounds.
Contents of the requirements.txt file:
Provide the requirements.txt file to help us find out module related issues.
Related information
Provide any related information