OASIS TC Open Repository: Manages TOSCA profiles, tests, and templates that are maintained by the TOSCA community. They are intended to be used as examples to help developers get started with TOSCA and to test compliance of TOSCA implementations with the standard.
The problem with the zip format is that it requires random access to unpack. So, unpacking a zip CSAR from a remote URL would require the user to first download the zip file. When zip files are large this can be problematic for certain platforms and devices. Adding support for tarballs would solve this problem.
There are various compression algorithms commonly used with tarballs. I propose at least supporting gzip explicitly in the spec, as it's the most widely supported. Implementations can of course support additional algorithms, too.
To allow for this we should allow CSAR files to have ".tar.gz" or ".tgz" extensions. For consistency, I thus propose that zip CSARs can also have the ".zip" extension.
For backward compatibility, a ".csar" extension will be considered to be a zip file.
The problem with the zip format is that it requires random access to unpack. So, unpacking a zip CSAR from a remote URL would require the user to first download the zip file. When zip files are large this can be problematic for certain platforms and devices. Adding support for tarballs would solve this problem.
There are various compression algorithms commonly used with tarballs. I propose at least supporting gzip explicitly in the spec, as it's the most widely supported. Implementations can of course support additional algorithms, too.
To allow for this we should allow CSAR files to have ".tar.gz" or ".tgz" extensions. For consistency, I thus propose that zip CSARs can also have the ".zip" extension.
For backward compatibility, a ".csar" extension will be considered to be a zip file.