Support floppy_content parameter

builder/vsphere/clone/builder.go

@@ -78,6 +78,7 @@ func (b *Builder) Run(ctx context.Context, ui packersdk.Ui, hook packersdk.Hook)
 			&commonsteps.StepCreateFloppy{
 				Files:       b.config.FloppyFiles,
 				Directories: b.config.FloppyDirectories,
+				Content:     b.config.FloppyContent,
 				Label:       b.config.FloppyLabel,
 			},
 			&common.StepAddFloppy{

builder/vsphere/common/step_add_floppy.go

@@ -21,6 +21,21 @@ type FloppyConfig struct {
 	FloppyFiles []string `mapstructure:"floppy_files"`
 	// List of directories to copy files from.
 	FloppyDirectories []string `mapstructure:"floppy_dirs"`
+	// 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.
+	//
+	// Usage example (HCL):
+	//
+	// ```hcl
+	// floppy_content = {
+	//   "meta-data" = jsonencode(local.instance_data)
+	//   "user-data" = templatefile("user-data", { packages = ["nginx"] })
+	// }
+	// ```
+	FloppyContent map[string]string `mapstructure:"floppy_content"`
 	// 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.

builder/vsphere/iso/builder.go

@@ -81,6 +81,7 @@ func (b *Builder) Run(ctx context.Context, ui packersdk.Ui, hook packersdk.Hook)
 		&commonsteps.StepCreateFloppy{
 			Files:       b.config.FloppyFiles,
 			Directories: b.config.FloppyDirectories,
+			Content:     b.config.FloppyContent,
 			Label:       b.config.FloppyLabel,
 		},
 		&common.StepAddFloppy{

docs-partials/builder/vsphere/common/FloppyConfig-not-required.mdx

@@ -8,6 +8,21 @@
 
 - `floppy_dirs` ([]string) - List of directories to copy files from.
 
+- `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.
+
+  Usage example (HCL):
+
+  ```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.