To prevent a name clash with a custom ProxyResource, network specs cannot use standard resource templates for new resources. We should create a mechanism where private dcorators and suppressions are not needed for new ntwork resources. This could be:
To prevent a name clash with a custom
ProxyResource, network specs cannot use standard resource templates for new resources. We should create a mechanism where private dcorators and suppressions are not needed for new ntwork resources. This could be:example: https://github.com/Azure/azure-rest-api-specs/pull/42717/changes#diff-ec5e52cdc9d434e2bde0ebd57ae1230d36275f3f638e3577065fcd9fda30d16e