Let apl-feed backup write to stdout via '-'#99
Merged
Conversation
Lets callers pipe the backup payload directly without an intermediate file. Same schema, no confirmation noise on stdout, no permissions or tempfile to manage.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
apl-feed backup -now writes the backup JSON straight to stdout instead of requiring a writable file path. Same schema as the file form, no confirmation message mixed in, and no umask/tempfile/rename dance to manage. Useful when a caller wants to consume the payload directly without staging a file on disk first.The existing
apl-feed backup <path>form keeps its prior behavior — the change is purely additive.