artifacts: exclude unused rubyzip test files from distributions #13431
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.
Release notes
[rn:skip]
What does this PR do?
Excludes unused testing artifacts from vendored
rubyzip
dependency, slightly reducing the size and surface-area of distributed artifacts.Backport targets:
8.0
,7.16
Why is it important/What is the impact to the user?
While the rubyzip testing fixtures are not on the load-path and inaccessible to the logstash process, some of the files they contain are occasionally picked up by automated scans. They are removed upstream in later releases of rubyzip (see: rubyzip/rubyzip#405), but for now we can exclude them from propagating into our distributed artifacts.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files (and/or docker env variables)[ ] I have added tests that prove my fix is effective or that my feature worksHow to test this PR locally
assemble*Distribution
gradle tasks, such as./gradlew assembleZipDistribution
vendor/bundle/jruby/2.5.0/gems/rubyzip-1.3.0
test
directory