Azure function not triggering with queue binding

Question

I have a working Azure WebJob with queue binding like this:

public static class Function1
{
    [FunctionName("Function1")]
    public static void Run([QueueTrigger("%input-queue%")]string myQueueItem, ILogger log)
    {
        log.LogInformation($"C# Queue trigger function processed: {myQueueItem}");
    }
}

I'm trying to convert it to an Azure Function. It works fine if I hard-code the queue name like [QueueTrigger("input")] but I want to make it configurable. Debugging locally works fine if I add the configuration to my local.settings.json file:

{
  "IsEncrypted": false,
  "Values": {
    "AzureWebJobsStorage": "",
    "FUNCTIONS_WORKER_RUNTIME": "dotnet",
    "input-queue": "debug-input"
  },
}

The problem is, I add "input-queue": "input" to my appsettings.json but the deployed function won't trigger. Am I doing something wrong here?

I have following FunctionStartup:

using Microsoft.Azure.Functions.Extensions.DependencyInjection;
using Microsoft.Extensions.Configuration;
using System.IO;

[assembly: FunctionsStartup(typeof(FunctionApp2.Startup))]

namespace FunctionApp2
{
    public class Startup : FunctionsStartup
    {
        public override void ConfigureAppConfiguration(IFunctionsConfigurationBuilder builder)
        {
            FunctionsHostBuilderContext context = builder.GetContext();

            builder.ConfigurationBuilder
                .AddJsonFile(Path.Combine(context.ApplicationRootPath, "appsettings.json"), optional: false, reloadOnChange: false)
                .AddJsonFile(Path.Combine(context.ApplicationRootPath, "local.settings.json"), optional: true, reloadOnChange: false)
                .AddEnvironmentVariables()
                .Build();
        }

        public override void Configure(IFunctionsHostBuilder builder)
        {
        }
    }
}

Here are my function app dependencies:

<ItemGroup>
    <PackageReference Include="Microsoft.Azure.Functions.Extensions" Version="1.1.0" />
    <PackageReference Include="Microsoft.Azure.WebJobs.Extensions.Storage" Version="3.0.4" />
    <PackageReference Include="Microsoft.Extensions.Configuration.Binder" Version="3.1.8" />
    <PackageReference Include="Microsoft.Extensions.Configuration.EnvironmentVariables" Version="3.1.8" />
    <PackageReference Include="Microsoft.Extensions.Configuration.Json" Version="3.1.8" />
    <PackageReference Include="Microsoft.NET.Sdk.Functions" Version="3.0.9" />
  </ItemGroup>

Answer 1

As discussed in the comments:

The appsettings.json file is not being read in when running in Azure Functions. Reading the local.settings.json when running locally, is part of the debugging experience of the Functions core tools.

Instead, when running in Azure, you should use the App Settings of Functions. This provides additional features such as Key Vault references.

Answer 2

Two things to point:

1, You didn't override abstract void Configure(IFunctionsHostBuilder builder), Your code will throw out error(And please make sure your function app start from Startup.cs by using assembly, have a look of this.).

2, Your code has no matter about add appsettings.json to environment variables. You read the value of the environment variable, but where is the setting?

Below code should work:

[assembly: FunctionsStartup(typeof(FunctionApp81.Startup))]
namespace FunctionApp81
{
    public class Startup : FunctionsStartup
    {
        public override void Configure(IFunctionsHostBuilder builder)
        {
            var text = File.ReadAllText("appsettings.json");
            var mydictionary = JsonConvert.DeserializeObject<Dictionary<string, string>>(text);
            foreach (var d in mydictionary)
            {
                Environment.SetEnvironmentVariable(d.Key,d.Value);
            }
        }

    }
}

Answer 3

@Kashyap The setting isn't visible in the portal. It should be coming from the appsettings.json file whereas the portal settings will be environment variables.

Looks like the way you publish/deploy your app to cloud is not publishing the app settings.

You can publish your settings in many ways. I prefer CLI, so two options are:

• az functionapp config appsettings
• func azure functionapp publish <app_name> --publish-settings-only --overwrite-settings: This one published settings from your local.settings.json to cloud.

There are many other options, including Portal.