Hacky fix of subresource for networking (#4430)

This fixes the SubResource from DnsResolver to match the SubResource from core networking so that we don't have a million different <Resource>SubResource's created. The issue is that dnsresolver and networking are two different Swagger specifications from two different Swagger folders that both put resources into the networking group. The 2022-07-01 API just happened to be supported by both networking and dnsresolver, but many subsequent API versions of plain networking don't correspond to a dnsresolver version. This results in inconsistencies between type names in the two versions of core networking which causes issues adding a new networking version due to conversion problems.
Azure · Nov 11, 2024 · 6a95721 · 6a95721
1 parent 8e7e143
commit 6a95721
Show file tree

Hide file tree

Showing 83 changed files with 2,071 additions and 3,644 deletions.
diff --git a/v2/api/network/v1api20201101/storage/load_balancers_inbound_nat_rule_types_gen.go b/v2/api/network/v1api20201101/storage/load_balancers_inbound_nat_rule_types_gen.go
diff --git a/v2/api/network/v1api20201101/storage/load_balancers_inbound_nat_rule_types_gen_test.go b/v2/api/network/v1api20201101/storage/load_balancers_inbound_nat_rule_types_gen_test.go
diff --git a/v2/api/network/v1api20201101/storage/structure.txt b/v2/api/network/v1api20201101/storage/structure.txt
@@ -1144,4 +1144,5 @@ augmentConversionForExtendedLocation: Interface
 augmentConversionForExtendedLocation_STATUS: Interface
 augmentConversionForIpTag: Interface
 augmentConversionForIpTag_STATUS: Interface
+augmentConversionForSubResource: Interface
 augmentConversionForSubResource_STATUS: Interface