Question about naming specific objects - subnet, route table, user defined route, etc.

[JamieSee]

In a tenant design with per application VNets, I've noticed that some objects don't seem to handle descriptive naming well. I was able to work around this by enabling the function name component on subnets and route tables; however, even with function enabled, user defined routes become differentiated only by the instance number in the current naming scheme provided by the tool even with the function name component enabled.

A Similar problem occurs for naming of VNet peering (peer) and VPN Gateway Connections (vcn). It's not uncommon for naming to be --peer or some variation of the above, but the tool cannot do repeated elements to accommodate this.

• How are other people working around this?
• Is some of this being moved to tagging instead of being included as a name component?
• Does it make sense to add a feature request to somehow support this?