We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For the zip archive type entrypoint.sh iterates over $INPUT_EXCLUSIONS to add a -x! argument per 'word'.
entrypoint.sh
$INPUT_EXCLUSIONS
-x!
But for the tar archive type it's just doing:
tar -zcvf $INPUT_FILENAME --exclude=$INPUT_EXCLUSIONS $INPUT_PATH
which means that every word after the first in INPUT_EXCLUSIONS instead is treated by tar as an input path, the exact opposite of what is wanted.
And if you use this with directory: '..' as I'm doing then you get errors like:
directory: '..'
tar: .editorconfig: Cannot stat: No such file or directory
because tar can't find the cited filenames/globs in order to use them as input files.
So, the same looping as is done for zip needs to be implemented for tar. For now I'm just going to use a manual script: | for my use case.
script: |
The text was updated successfully, but these errors were encountered:
Hello @Athanasius. Thank you for pointing out the issue with handling multiple exclusions for tar - I just implemented it.
tar
Sorry, something went wrong.
TheDoctor0
No branches or pull requests
For the zip archive type
entrypoint.sh
iterates over$INPUT_EXCLUSIONS
to add a-x!
argument per 'word'.But for the tar archive type it's just doing:
which means that every word after the first in INPUT_EXCLUSIONS instead is treated by tar as an input path, the exact opposite of what is wanted.
And if you use this with
directory: '..'
as I'm doing then you get errors like:because tar can't find the cited filenames/globs in order to use them as input files.
So, the same looping as is done for zip needs to be implemented for tar. For now I'm just going to use a manual
script: |
for my use case.The text was updated successfully, but these errors were encountered: