Hi,

I'm trying to direct the output of to stdout, so that I can pipe it into gpg in order to encrypt it.

If I do:
of course I would end up with both vagrant.box and vagrant.box.gpg.
I also tried mkfifo /tmp/pipe, but running --output /tmp/pipe says (obviously) that the file already exists and that I should choose another path.

I'm trying to create encrypted backups, so I would have liked to avoid having to delete the unecrpyted backup afterwards, let alone the unncessary second process (which is gpg which created another file altogether).

Any ideas?

I know nothing about vagrant, but a quick look at online docs suggests that writing it to a file is not optional - that is it writes to package.box by default, or to the named file if --output is given, but I see no provision for sending it to stdout.

Maybe you could write a simple wrapper script to handle the whole process and remove the intermediate file.

I've already done that, actually, but I was wondering if bash had the means to somehow trick it into sending the output to stdout and then pipe it into another command. As I've already mentioned, it means that the process takes too long, because I generate two files instead of one and I need to delete one afterwards. On the other hand, if the command doesn't support it, there might be no way of solving it, especially given the fact that it also outputs reports of what is doing: shutting down the machine gracefully etc. So now that I think about it, it can't work, because the command runs several commands and checks.