[FEATURE REQ] firewallPolicy draft and rule collection group draft should be sub resource for its corresponding policy resource. #31857
Labels
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
feature-request
This issue requires a new behavior in the product in order be resolved.
Mgmt
This issue is related to a management-plane library.
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
API Spec link
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/network/resource-manager/Microsoft.Network/stable/2023-11-01/firewallPolicy.json
API Spec version
2023-11-01
Please describe the feature.
Hi, with the current spec design, it seems like both firewallPolicy draft and rule collection group draft have its own CRUD APIs, but they should be treated like other sub-resources (same as rule collection group): policy draft as a sub resource of policy, and rule collection group draft as a sub-resource of rule collection group (which itself is a sub-resource of firewallpolicy).
i.e. The structure should be:
firewallPolicy
a. firewallPolicy draft
b. rule collection group
(1). rule collection group draft
References
hashicorp/go-azure-sdk#1055
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/network/resource-manager/Microsoft.Network/stable/2023-11-01/firewallPolicy.json
https://pkg.go.dev/github.com/hashicorp/go-azure-sdk/[email protected]/network/2023-11-01
The text was updated successfully, but these errors were encountered: