feature: add extract command to extract embedded tool binaries #624
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.
This pull request introduces a new developer-facing CLI command to extract embedded script resources, and adds supporting utility code to handle resource extraction from the embedded filesystem. The changes are organized into two main themes: CLI enhancements and utility function additions.
CLI Enhancements:
extractcommand to the CLI (extractCmdincmd/root.go). This command allows developers to extract all embedded script resources to a specified output directory for inspection or modification. [1] [2]internal/scriptpackage.Utility Function Additions:
ExtractAllResourcesininternal/util/util.go, which recursively walks the embedded filesystem and extracts all resources as files into the specified directory, supporting the newextractcommand.