github.com/hashicorp/packer@v1.14.3/website/content/partials/packer-plugin-sdk/multistep/commonsteps/FloppyConfig-not-required.mdx (about) 1 <!-- Code generated from the comments of the FloppyConfig struct in multistep/commonsteps/floppy_config.go; DO NOT EDIT MANUALLY --> 2 3 - `floppy_files` ([]string) - A list of files to place onto a floppy disk that is attached when the VM 4 is booted. Currently, no support exists for creating sub-directories on 5 the floppy. Wildcard characters (\\*, ?, and \[\]) are allowed. Directory 6 names are also allowed, which will add all the files found in the 7 directory to the floppy. 8 9 - `floppy_dirs` ([]string) - A list of directories to place onto the floppy disk recursively. This is 10 similar to the `floppy_files` option except that the directory structure 11 is preserved. This is useful for when your floppy disk includes drivers 12 or if you just want to organize it's contents as a hierarchy. Wildcard 13 characters (\\*, ?, and \[\]) are allowed. The maximum summary size of 14 all files in the listed directories are the same as in `floppy_files`. 15 16 - `floppy_content` (map[string]string) - Key/Values to add to the floppy disk. The keys represent the paths, and 17 the values contents. It can be used alongside `floppy_files` or 18 `floppy_dirs`, which is useful to add large files without loading them 19 into memory. If any paths are specified by both, the contents in 20 `floppy_content` will take precedence. 21 22 Usage example (HCL): 23 24 ```hcl 25 floppy_files = ["vendor-data"] 26 floppy_content = { 27 "meta-data" = jsonencode(local.instance_data) 28 "user-data" = templatefile("user-data", { packages = ["nginx"] }) 29 } 30 floppy_label = "cidata" 31 ``` 32 33 - `floppy_label` (string) - Floppy Label 34 35 <!-- End of code generated from the comments of the FloppyConfig struct in multistep/commonsteps/floppy_config.go; -->