Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zed backup create to existing file #329

Open
FrankFoerster24 opened this issue Jan 18, 2024 · 0 comments
Open

zed backup create to existing file #329

FrankFoerster24 opened this issue Jan 18, 2024 · 0 comments
Labels
hint/good first issue Someone new could handle this priority/3 low This would be nice to have

Comments

@FrankFoerster24
Copy link

FrankFoerster24 commented Jan 18, 2024

Hi,

I've reported this already in #284, but I found the solution and implementation there insufficient.

I'd love zed backup create to write to an existing file, maybe protected by a --force, for example a previously created /path/to/some/fifo where other processes can read the output from for further processing. Quoting the full description from the other issue:

I'd like to run backups using the provided docker images which don't have much other utilities, not even a shell to > redirect the stream on stdout AFAIK. I'm not keen to run my own images. The pattern I usually would use is that I send the data to a named pipe (created by mkfifo on a shared volume in an init container), have the zed container write to it and another container in the same pod read from it for further processing (compression, encryption, etc.). With zed refusing to write to the existing named pipe I cannot do that.

Let me know if you require any further information.

Kind regards,
Frank.

@jzelinskie jzelinskie added hint/good first issue Someone new could handle this priority/3 low This would be nice to have labels Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hint/good first issue Someone new could handle this priority/3 low This would be nice to have
Projects
None yet
Development

No branches or pull requests

2 participants