How to with the latest FunctionsApplicationBuilder?

[NetRushJacob]

Latest function app creation (.net 8/9 isolated) shift from HostBuilder to FunctionsApplicationBuilder, which doesn't have a method to access the internal HostBuilder nor does it provide a ConfigureFunctionsWebApplication method that allows the addition of middleware to the HostBuilder.

var builder = FunctionsApplication.CreateBuilder(args);

builder.ConfigureFunctionsWebApplication();

Does Dark Loop support this latest shift?

[artmasa]

Hi @NetRushJacob,

The short answer to your question is yes.

You will need to add a reference to Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore to your project.
Here is a snippet of the modified sample Isolated project:

var builder = FunctionsApplication.CreateBuilder([]);

builder.ConfigureFunctionsWebApplication();
builder.UseFunctionsAuthorization();
builder.Services
    .AddFunctionsAuthentication(JwtFunctionsBearerDefaults.AuthenticationScheme)
    .AddJwtFunctionsBearer(options =>
    {
        // this line is here to bypass the token validation
        // and test the functionality of this library.
        // you can create a dummy token by executing the GetTestToken function in HelperFunctions.cs
        // THE FOLLOWING LINE SHOULD BE REMOVED IN A REAL-WORLD SCENARIO
        options.SecurityTokenValidators.Add(new TestTokenValidator());

        // this is what you should look for in a real-world scenario
        // comment the lines if you cloned this repository and want to test the library
        options.Authority = "https://login.microsoftonline.com/<your-tenant>";
        options.Audience = "<your-audience>";
        options.TokenValidationParameters = new TokenValidationParameters
        {
            ValidateIssuer = true,
            ValidateAudience = true,
            ValidateLifetime = true,
            ValidateIssuerSigningKey = true,
        };
    });

builder.Services
    .AddFunctionsAuthorization(options =>
    {
        // Add your policies here
    });
    

var host = builder.Build();
host.Run();

You can notice that you can invoke UseFunctionsAuthorization() directly on FunctionsApplicationBuilder, but you need to invoke ConfigureFunctionsWebApplication(). I don't think Configure... is the best name as you are not configuring any builder with it; maybe EnableFunctionsWebApplication() would have been a better option.

I have tested this approach and it works. I will add another sample project for this new API.

Hope this helps

[NetRushJacob]

Perfect, thank you for this! We're implementing into our current functions now.