pulumi-azure

pulumi-azure copied to clipboard

https://github.com/pulumi/pulumi-azure/blob/151eba6e19cc41e70cbc5ffb1817cb777649ead9/sdk/nodejs/appservice/zMixins.ts#L397

With Azure Function App version ~4 the extension bundle version needs to be updated accordingly. Currently, no support to specify the extension bundle version.

https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-register#extension-bundles

Maybe I am missing how to configure it?

Hi @imbelchev, thanks for raising this. It doesn't seem that it can be configured currently.

I'm not a Functions expert. Would it be enough to change the version range to [1.*, 4.*] or similar? Or do different users need different ranges?

Hi @thomas11,

Thanks for the fast replay.

I am not really a big expert on Azure Functions as well but, from how I understand things - if bundle version [1.*, 4.*] is specified - it should automatically pick up the correct version based on the specified runtime version (configured by this readonly version?: pulumi.Input<string>;).

Supported major versions of Azure Functions:

• Functions v1 is still in support.
• Functions v2 is no longer supported.
• Functions v3 - Beginning on December 13, 2022 - EOL of extended support. Function apps are not eligible for new features, security patches, and performance optimizations. No service support is provided for this version (Migrate apps from Azure Functions version 3.x to version 4.x).
• Functions v4 is the recommended one.

So I have tested this. There is a mapping runtime version : extension bundle version provided by Microsoft which needs to be strictly followed. It's from the same link posted in the issue initially - Register Azure Functions binding extensions

@thomas11 ,

Are these changes enough to accept the PR and release a new version? https://github.com/pulumi/pulumi-azure/pull/1202

@thomas11 , @mikhailshilkov , As the contribution was accepted and PR merged, do you have any timeline for when this change might get to an actual public release?

PS: No rush here, just trying to have some expected timelines so I can update our team accordingly.

@thomas11 , @mikhailshilkov , As the contribution was accepted and PR merged, do you have any timeline for when this change might get to an actual public release?

@imbelchev It should be out by the end of the week unless something unexpected happens.

@thomas11 , awesome ❤️

Thank you!