Skip to content

[AVM Module Issue]: Improve (fix) naming on Virtual Wan Hub Connections #3085

@noopman

Description

@noopman

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

Metadata

Metadata

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions