-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Add delegation support to virtual network subnet blocks #24972
Add delegation support to virtual network subnet blocks #24972
Conversation
- Implemented delegation configuration in virtual_network_resource.go to allow specifying delegation services and actions for subnets within virtual networks. - Updated tests in virtual_network_resource_test.go to cover the new delegation functionality in the subnet blocks. - Documented the delegation feature in virtual_network.html.markdown, providing users with guidance on how to use this new capability. - Adjust related subnet resource code in subnet_resource.go for compatibility and consistency with virtual network changes. This enhancement enables users to configure service delegations for subnets directly in the blocks, supporting scenarios that require specialized services such as Azure Container Instances or Azure NetApp Files to be associated with specific subnets.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
To align our organization with the Azure Cloud Adoption Framework (CAF) and adhere to Azure Policies, we've employed Terraform modules for streamlined network security and service deployments. A central aspect of this strategy is the deployment of vNet spokes connected to our central Hub. These spokes must support Microsoft Fabric and Container Apps, necessitating the ability to delegate subnets for seamless service integration. Challenge with current separation between subnet and vNet resources A key challenge stems from the Azure policy Subnets should be associated with a Network Security Group. This mandates the attachment of Network Security Groups (NSGs) at the time of subnet creation. Due to this requirement, vNet creation becomes complex as it cannot proceed without pre-defined subnets and associated NSGs, demanding an integrated approach from the very beginning. The current design of the Potential Solution A potential solution lies in extending the Let me know your thoughts |
hey @rickardl Thanks for this PR. The Whilst we’re planning to extend the All of that is to say, whilst we’d like to thank you for this contribution - and this is something we plan to support in the future - since we’re still waiting to head about the dependencies, unfortunately we’re going to need to mark this one as Thanks! |
Related: #25765 |
Closing in favour of #26533 |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
virtual_network_resource.go
to allow specifying delegation services and actions for subnets within virtual networks.virtual_network_resource_test.go
to cover the new delegation functionality in the subnet blocks.virtual_network.html.markdown
, providing users with guidance on how to use this new capability.subnet_resource.go
for compatibility and consistency with virtual network changes.This enhancement enables users to configure service delegations for subnets directly in the blocks, supporting scenarios that require specialized services such as Azure Container Instances or Azure NetApp Files to be associated with specific subnets.
Attempts to resolve #25025