Allow to use maps for disk definitions

This changes the disk block in the domain resource to be defined as a map,
instead of an object. There is no difference in the standard use case,
but it allows to generate disk maps via interpolations and variables
which is useful in modules.

1 files changed, 35 insertions, 0 deletions

diff --git a/docs/providers/libvirt/r/domain.html.markdown b/docs/providers/libvirt/r/domain.html.markdown
index d5fb93a2..e169c4dc 100644
--- a/docs/providers/libvirt/r/domain.html.markdown
+++ b/docs/providers/libvirt/r/domain.html.markdown
@@ -110,6 +110,41 @@ resource "libvirt_domain" "domain1" {
 }
 ```
 
+Also note that the `disk` block is actually a list of maps, so it is possible to declare several, use the literal list and map syntax or variables and interpolations, as in the following examples.
+
+```
+resource "libvirt_domain" "my_machine" {
+  ...
+  disk {
+    volume_id = "${libvirt_volume.volume1.id}"
+  }
+  disk {
+    volume_id = "${libvirt_volume.volume2.id}"
+  }
+}
+```
+
+```
+resource "libvirt_domain" "my_machine" {
+  ...
+  disk = [
+    {
+      volume_id = "${libvirt_volume.volume1.id}"
+    },
+    {
+      volume_id = "${libvirt_volume.volume2.id}"
+    }
+  ]
+}
+```
+
+```
+resource "libvirt_domain" "my_machine" {
+  ...
+  disk = ["${var.disk_map_list}"]
+}
+```
+
 The `network_interface` specifies a network interface that can be connected either to
 a virtual network (the preferred method on hosts with dynamic / wireless networking
 configs) or directly to a LAN.