[docs] floppy_content docs

Author: imranh2

.web-docs/components/builder/iso/README.md

@@ -236,6 +236,21 @@ In HCL2:
   your floppy disk includes drivers or if you just want to organize it's
   contents as a hierarchy. Wildcard characters (\*, ?, and \[\]) are allowed.
 
+- `floppy_content` (map[string]string) - Key/Values to add to the floppy disk. The keys represent the paths, and
+  the values contents. It can be used alongside `floppy_files` or
+  `floppy_dirs`, which is useful to add large files without loading them
+  into memory. If any paths are specified by both, the contents in
+  `floppy_content` will take precedence.
+  
+  HCL Example:
+  
+  ```hcl
+  floppy_content = {
+    "meta-data" = jsonencode(local.instance_data)
+    "user-data" = templatefile("user-data", { packages = ["nginx"] })
+  }
+  ```
+
 - `floppy_label` (string) - The label to use for the floppy disk that
   is attached when the VM is booted. This is most useful for cloud-init,
   Kickstart or other early initialization tools, which can benefit from labelled floppy disks.

.web-docs/components/builder/pvm/README.md

@@ -88,6 +88,21 @@ can also be supplied to override the typical auto-generated key:
   your floppy disk includes drivers or if you just want to organize it's
   contents as a hierarchy. Wildcard characters (\*, ?, and \[\]) are allowed.
 
+- `floppy_content` (map[string]string) - Key/Values to add to the floppy disk. The keys represent the paths, and
+  the values contents. It can be used alongside `floppy_files` or
+  `floppy_dirs`, which is useful to add large files without loading them
+  into memory. If any paths are specified by both, the contents in
+  `floppy_content` will take precedence.
+  
+  HCL Example:
+  
+  ```hcl
+  floppy_content = {
+    "meta-data" = jsonencode(local.instance_data)
+    "user-data" = templatefile("user-data", { packages = ["nginx"] })
+  }
+  ```
+
 - `floppy_label` (string) - The label to use for the floppy disk that
   is attached when the VM is booted. This is most useful for cloud-init,
   Kickstart or other early initialization tools, which can benefit from labelled floppy disks.

docs/builders/iso.mdx

@@ -124,6 +124,21 @@ can also be supplied to override the typical auto-generated key:
   your floppy disk includes drivers or if you just want to organize it's
   contents as a hierarchy. Wildcard characters (\*, ?, and \[\]) are allowed.
 
+- `floppy_content` (map[string]string) - Key/Values to add to the floppy disk. The keys represent the paths, and
+  the values contents. It can be used alongside `floppy_files` or
+  `floppy_dirs`, which is useful to add large files without loading them
+  into memory. If any paths are specified by both, the contents in
+  `floppy_content` will take precedence.
+  
+  HCL Example:
+  
+  ```hcl
+  floppy_content = {
+    "meta-data" = jsonencode(local.instance_data)
+    "user-data" = templatefile("user-data", { packages = ["nginx"] })
+  }
+  ```
+
 - `floppy_label` (string) - The label to use for the floppy disk that
   is attached when the VM is booted. This is most useful for cloud-init,
   Kickstart or other early initialization tools, which can benefit from labelled floppy disks.

docs/builders/pvm.mdx

@@ -98,6 +98,21 @@ can also be supplied to override the typical auto-generated key:
   your floppy disk includes drivers or if you just want to organize it's
   contents as a hierarchy. Wildcard characters (\*, ?, and \[\]) are allowed.
 
+- `floppy_content` (map[string]string) - Key/Values to add to the floppy disk. The keys represent the paths, and
+  the values contents. It can be used alongside `floppy_files` or
+  `floppy_dirs`, which is useful to add large files without loading them
+  into memory. If any paths are specified by both, the contents in
+  `floppy_content` will take precedence.
+  
+  HCL Example:
+  
+  ```hcl
+  floppy_content = {
+    "meta-data" = jsonencode(local.instance_data)
+    "user-data" = templatefile("user-data", { packages = ["nginx"] })
+  }
+  ```
+
 - `floppy_label` (string) - The label to use for the floppy disk that
   is attached when the VM is booted. This is most useful for cloud-init,
   Kickstart or other early initialization tools, which can benefit from labelled floppy disks.