uyuni-project
Re-evaluate decision of using maps to specify domain-volume associations in libvirt
REQUIRES: https://github.com/moio/sumaform/issues/75
Using maps is handy for module code reuse, and was implemented in terraform-provider-libvirt for this reason.
On the other hand, it has the downside of always needing different resources for volumes and domains, even in case one doesn't make sense without the other (eg. root disks). terraform taint must always be executed twice, terraform state list is more complicated than it should be, etc.
If we decide not to use nested modules anymore we might contribute code to terraform-provider-libvirt for resources that represent "essential" domain-volume associations as it happens eg. in the AWS, Azure and Google Cloud providers.
Expected behaviour is to have only one resource that accounts for the VM and its root volume(s), that is created, destroyed, tainted as a whole.
