-
Notifications
You must be signed in to change notification settings - Fork 522
Closed
Labels
Class: Pattern Module 📦This is a pattern moduleThis is a pattern moduleStatus: In PR 👉This is when an issue is due to be fixed in an open PRThis is when an issue is due to be fixed in an open PRType: AVM 🅰️ ✌️ Ⓜ️This is an AVM related issueThis is an AVM related issueType: Feature Request ➕New feature or requestNew feature or request
Description
Check for previous/existing GitHub issues
- I have checked for previous/existing GitHub issues
Issue Type?
Feature Request
Module Name
avm/ptn/lz/sub-vending
(Optional) Module Version
No response
Description
The naming of Virtual Wan Hub Connections is based on a guid. It looks incredibly ugly in the list of connections. Real world example: vhc-48b529d4-e9c0-5a89-87d8-a413512e103f
I propose:
- Make much better names for the connection using the vnet name as part of the connection name by default!
- Consider allowing the connection name to be an optional parameter!
Here is the exact location in code where the virtualWanHubConnectionName is set.
var virtualWanHubConnectionName = 'vhc-${guid(virtualHubResourceIdChecked, virtualNetworkName, virtualNetworkResourceGroupName, virtualNetworkLocation, subscriptionId)}'
Instead we could have 'cn' for connection and the name could be as simple as this:
var virtualWanHubConnectionName = 'cn-${virtualNetworkName}'
(Optional) Correlation Id
No response
RS-MPersson
Metadata
Metadata
Labels
Class: Pattern Module 📦This is a pattern moduleThis is a pattern moduleStatus: In PR 👉This is when an issue is due to be fixed in an open PRThis is when an issue is due to be fixed in an open PRType: AVM 🅰️ ✌️ Ⓜ️This is an AVM related issueThis is an AVM related issueType: Feature Request ➕New feature or requestNew feature or request
Type
Projects
Status
Done