-
Bug
-
Resolution: Done
-
Medium
-
Frankfurt Release
-
None
Some tar libraries compress (current) folder so that it looks like this:
. file2.txt dir1/ dir1/file1.txt
While most libraries provide such format:
./ ./file2.txt ./dir1/ ./dir1/file1.txt
Tar tools handle leading "." item by substituting it with empty string. In case of first example this would provide such handling by GNU Tar (different example tar):
k.banka@AMDC3701:[0]$ base64 -d <<< "H4sIAAAAAAAA/+2UzQrDIBCEPfsUS+4pa0wUfJki1EIgPyWaQN4+kpwaCjk0sYfud1HWw4yMI2PXgwJRlSXgxn5d90IqiWWlsSriXCssGGACb2z0wQ4Mv9baX+4EaylobVc/nQ+32bbNRRqH+Sv9nr8oJGrKPwV5nvPJDb7uOwOT4GF+OcMBJtuMzhvI+ng61A933ybrO8n4r20TJ/Ep3rM1Dvsv1K7/UmlB/U9BiH//lr0BTbUmCIL4Gxa2F0VhAA4AAA==" | tar -tz
tar: Substituting `.' for empty member name
manifest.yaml
override_values.yaml
That is, with warning message, it handles archive succesfully, but one of the item is "", that is skipped.
The point of this task is to correct handling of such archives in k8splugin archive library.
- relates to
-
INT-1457 Integrate end to end vFW_CDS_CNF usecase
- Closed