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.

Sign up for GitHub

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

Jump to bottom

[Feature]: New-AzFunctionApp should support VNet integration during function app creation. #26848

Open
Francisco-Gamino opened this issue Dec 6, 2024 · 4 comments
Open

[Feature]: New-AzFunctionApp should support VNet integration during function app creation. #26848

Francisco-Gamino opened this issue Dec 6, 2024 · 4 comments
Labels
feature-request This issue requires a new behavior in the product in order be resolved. Functions Service Attention This issue is responsible by Azure service team.

Comments

@Francisco-Gamino
Copy link
Contributor

Description of the new feature

New-AzFunctionApp should support VNet integration during function app creation. This new parameter should be available for all SKUs, except for Consumption V1.

The Az CLI supports the --vnet and --subnet parameters for these scenarios. Consider adding an equivalent in New-AzFunctionApp.

Proposed implementation details (optional)

No response
@Francisco-Gamino Francisco-Gamino added feature-request This issue requires a new behavior in the product in order be resolved. needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Dec 6, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Dec 6, 2024
@Francisco-Gamino
Copy link
Contributor Author

/cc @im-samz

@im-samz
Copy link

im-samz commented Dec 6, 2024

Love this! We'll also need set different properties for each hosting plan:

  • Consumption --> fail if customer tries to supply this parameter
  • Flex Consumption --> set vnet: <SUBNET_RESOURCE_ID
  • Premium --> set vnet: <SUBNET_RESOURCE_ID>; vnetRouteAllEnabled: true; vnetContentShareEnabled: true
  • Dedicated --> set vnet: <SUBNET_RESOURCE_ID>; vnetRouteAllEnabled: true
  • Container Apps --> (I need to circle back on this)

@isra-fel isra-fel added Service Attention This issue is responsible by Azure service team. Functions labels Dec 12, 2024
@microsoft-github-policy-service Microsoft GitHub Policy Service
Copy link
Contributor

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @AnatoliB, @Francisco-Gamino, @shreyabatra4.

1 similar comment
@microsoft-github-policy-service Microsoft GitHub Policy Service
Copy link
Contributor

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @AnatoliB, @Francisco-Gamino, @shreyabatra4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature-request This issue requires a new behavior in the product in order be resolved. Functions Service Attention This issue is responsible by Azure service team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@isra-fel @Francisco-Gamino @im-samz