Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Environment variable WEBSITE_OWNER_NAME changed in Azure Functions on Consumption Flex plan #10441

Open
Bataran opened this issue Aug 30, 2024 · 2 comments

Comments

@Bataran
Copy link

Bataran commented Aug 30, 2024

Is your question related to a specific version? If so, please specify:

Tested on Node.js 20x on Consumpltion Flex plan

What language does your question apply to? (e.g. C#, JavaScript, Java, All)

Node.js, but most likely other languages too

Question

It seems that WEBSITE_OWNER_NAME environment variable format changed on the new Consumption Flex plan. The new format is something like this:
<subscription-id>+flex-99ddf98v18fee2c3d86cb4d0f37573099297d5124520437bfa4ee00d9fc8ff8e-webspace
comparing to the format on the old Consumption plan:
<subscription-id>+<resource-group>-<region>webspace-Linux

Since the variable is not publicly documented it's expected to change, but still it was the only way to get resource group from within the function (without fetching it from other sources).

The question is: should we expect to have the new format also in the old Consumption plan (not Flex)? If yes, will users have some other way to obtain resource group within the function as also the WEBSITE_RESOURCE_GROUP is missing in both Consumption and Consumption Flex plans?

@JAdluri
Copy link

JAdluri commented Dec 19, 2024

Hello @Bataran thank you for reporting will check and let you know further steps.

@JAdluri
Copy link

JAdluri commented Dec 20, 2024

Hello could you pl. check now on the same issue if its still existing as i didnt encouter this kind of issue when i tried to reproduce the same thing on my end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants