[azure provider] ability to add azure subnet configuration
Bug #1892490 reported by
Peter Jose De Sousa
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Wishlist
|
Ian Booth |
Bug Description
Hi,
When creating juju subnets the azure provider creates two resources with regards to networking: the vNet and a subnet within that vNet. There are requirements where this subnet and vNet names are required to be changed.
Much like the resource group change, this could take the form of a configuration or existing subnet name.
I would say letting juju creating this should take precident, in keeping with the juju paradigm and keeping the generic case supported.
Cheers!
Peter
summary: |
- [azure provider] ability to add azure subnet names + [azure provider] ability to add azure subnet configuration |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Building on top of this, we are now dealing with a case there there is a central resource group (Spoke network) with vNets already deployed.
The vNets in this spoke resource group would then be used by the juju VMs (specified in a model configuration).