[RFE - Azure] Custom naming convention when creating VMS
Bug #1914589 reported by
Peter Jose De Sousa
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Hi,
We're seeing a requirement in field when creating new VMs on Azure with juju that these new VMs follow a naming convention. Ideally, this would be a static naming convention as a first pass e.g. MY-NAMING-
Then moving to a 'progammable' one later e.g. {MY-CONTROLLER-
Cheers,
Peter
tags: | added: azure-provider |
To post a comment you must log in.
Assuming {NUMBER} is like for units where it's monotonically increasing, there would need to be a place to store the previously used number etc. There's an argument that doing this work could be considered holistically across all providers, not just Azure, given the need to tweak the model to deal with the next number to use etc.
It's not necessarily super hard to do, but not totally trivial either given the doc and testing that would need to go along with it.