Hello,
I cannot seem to find a way to leverage App Configuration for properties that are used in my Azure Function bindings. For example, in the code snippet below, I would like to use App Configuration to serve up the value for the AzureCosmosDBConnection setting in my output binding. I would rather not get in a situation where I need to define some of my properties as "Application Settings" and some in "App Configuration". The situation below seems to be that Function bindings get resolved at build time and the App Configuration values are not available at that time? What is considered the best practice for serving up the values required by function bindings vs other properties your function might need? Like I said, it doesn't feel right that we would need to use multiple solutions for doing this, would love to be able to use App Configuration for everything!
@FunctionName("HttpExample")
public HttpResponseMessage run(
@HttpTrigger(
name = "req",
methods = {HttpMethod.GET, HttpMethod.POST},
authLevel = AuthorizationLevel.ANONYMOUS)
HttpRequestMessage<Optional<String>> request,
@CosmosDBOutput(
name = "database",
databaseName = "%databaseName%",
collectionName = "my-collection",
connectionStringSetting = "AzureCosmosDBConnection")
OutputBinding<List<CosmosFramework>> cosmosOutput,
final ExecutionContext context
)