update naming conventions to prevent from naming conflicts
JaydenLiang opened this issue · 0 comments
JaydenLiang commented
background:
regarding upgrading autoscale deployment from old version to new version, some resources naming in the current implementation will become conflicting with others.
will resolve it by using a per resource name prefix naming convention in all resources:
vmss (new format: uniqueResourceNamePrefix-vmss-payg001)
cosmos db (new format: uniqueResourceNamePrefix-dba001)
function app (new format: uniqueResourceNamePrefix-funcapp001)
app insight (new format: uniqueResourceNamePrefix-appins001)
app service plan (new format: uniqueResourceNamePrefix-appserplan001)
key vault (new format: uniqueResourceNamePrefix-kv001)