Closed colinbowern closed 9 years ago
This behavior comes from Packer. From the documentation on packer.io:
floppy_files (array of strings) - A list of files to place onto a floppy
disk that is attached when the VM is booted. ... All files listed in this
setting get placed into the root directory of the floppy and the floppy
is attached as the first floppy device. ... Wildcard characters(*, ?,
and []) are allowed. Directory names are also allowed, which will add
all the files found in the directory to the floppy.
It would be odd to try to support paths with wildcards and URLs.
Yeah it's a bit of a strange one. The best we could offer would be to simplify the floppy files behaviour which would make us divergent from upstream Packer. As we have a goal to some day merge this into upstream Packer I'm not sure this is a good idea I'm afraid to say.
@colinbowern please address this as an issue at mitchellh/packer and we'll gladly follow along. Until then, we're not going to diverge our behavior here.
The template has different rules for file paths which makes it difficult to manage. When referring to files the same rules should apply to floppy_files collection as it does to the iso_url field. Trying the file:/// format results in the following errors:
Please use consistent path parsing across all of packer and its plugins.