You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When VMs, NIC/VNETs, etc. are all created, the default naming scheme is:
<resource_group_name>-<tag>[-nic/-vnet]
This is useful, but if the Resource Group name is long, or would look cluttered in the above format, then it's hardly ideal.
This issue is to introduce a parameter into the template files of "pretag", which if present will override the usage of the Resource Group name being used in all resource creation:
<pretag>-<tag>[-nic/-vnet]
This means, that if your group name were "test-web-rg" and you wanted a VM with tag "web", you'd get "test-web-web1" which looks a little silly. Whereas if you set the pretag to be "test" then you'd have "test-web1" which looks a little better!
The text was updated successfully, but these errors were encountered:
When VMs, NIC/VNETs, etc. are all created, the default naming scheme is:
This is useful, but if the Resource Group name is long, or would look cluttered in the above format, then it's hardly ideal.
This issue is to introduce a parameter into the template files of
"pretag"
, which if present will override the usage of the Resource Group name being used in all resource creation:This means, that if your group name were
"test-web-rg"
and you wanted a VM with tag"web"
, you'd get"test-web-web1"
which looks a little silly. Whereas if you set the pretag to be"test"
then you'd have"test-web1"
which looks a little better!The text was updated successfully, but these errors were encountered: