feat(export): bundle multi-subnet export into a zip with a combined txt - #31
Merged
Conversation
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
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.
What changed
<category>.txtper subnet plus anALL_<qty>.txtconcatenating every proxy line for easy bulk import.XX/MIXED, then the subnet and proxy counts, and a short scope fingerprint so distinct selections never silently overwrite each other while re-exporting the same scope replaces its own archive.archive.rsowns ZIP serialization (deflate, owner-only permissions inside and out);secure_fileexposes the shared truncating 0600 opener; export planning stays pure and tested.Why
One downloadable artifact per export makes multi-subnet hand-off to bulk-import tools a single step instead of gathering many files.
Test plan