What would you like to be added:
When adding binaries (tools, executables) to an OCM CV, in the constructor we can mark them to be compressed during packaging:
components:
- name: foo
resources:
- name: bar
input:
type: file
compress: trueHowever, when using ocm download resource, the raw stored blob will be saved to the filesystem, the compression is not being handled, and it should be.
I think a flag should be added to ocm download resource, which ensures that the saved binary is uncompressed (if it is not compressed, then it's a noop / if compressed, then it uncompresses it).
Why is this needed:
Operators, who are receiving tooling through OCM-packaged shipments are not interested in having the most complicated ways to access their resources. They are interested in easy-to-use, fluid, ergonomic environments, which are positively contributing to their productivity. Enforcing unnecessary steps (such us verify and if compressed, uncompress) certain things is doing the opposite.
What would you like to be added:
When adding binaries (tools, executables) to an OCM CV, in the constructor we can mark them to be compressed during packaging:
However, when using
ocm download resource, the raw stored blob will be saved to the filesystem, the compression is not being handled, and it should be.I think a flag should be added to
ocm download resource, which ensures that the saved binary is uncompressed (if it is not compressed, then it's a noop / if compressed, then it uncompresses it).Why is this needed:
Operators, who are receiving tooling through OCM-packaged shipments are not interested in having the most complicated ways to access their resources. They are interested in easy-to-use, fluid, ergonomic environments, which are positively contributing to their productivity. Enforcing unnecessary steps (such us verify and if compressed, uncompress) certain things is doing the opposite.