Comments (2)
Thanks for filing this! The v0.13.0 release should support this now.
from zed.
Hi,
thank you very much for the swift implementation. However, for completeness I'd like to add that I still have the use case to send the backup data to an existing file (which is AFAICS not possible right now).
This is my use case: 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.
I'll find workarounds, but the described pattern would be fit most perfectly for me. Let me know how to proceed (reopen this issue, create a new one, go away and leave you alone... ;-)).
Thanks again and kind regards,
Frank.
from zed.
Related Issues (20)
- zed permission lookup-subjects is causing a segfault HOT 3
- Exporting schema and relationships in a format that is compatible with zed import HOT 1
- Print "success" if error code is 0 HOT 2
- Make docs for cli
- Add a curl-like command that uses the zed context
- Make documentation and error more clear when trying to execute zed without context HOT 2
- --certificate-path flag is not respected
- Store backup snapshot timestamp in the backupfile
- Proper signal handling for backup and restore operations
- Validate `.zaml` file should support sourcing schema from a file HOT 2
- Add argument to zed validate to auto-create playground link
- The context token doesn't appear to be using the stored NoVerifyCA and CACert
- zed command relationship read, could not use the subject option without giving the relation option HOT 1
- zed backup create to existing file
- Package shell completion into DEB and RPM
- add retries on serialization errors for write operations
- Some errors seem to always be in json, even if using an interactive shell HOT 1
- zed import ignores value of --schema-definition-prefix when referencing caveats
- Support command shorthands HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from zed.