Infrastructure/zot
0
Fork 0
mirror of https://github.com/project-zot/zot.git synced 2024-12-16 21:56:37 -05:00
Code Issues Activity
zot/pkg/storage
History
Andrei Aaron faa410a0c3
feat(cli): Fix multiple issues with zli output (#1612) 
https://github.com/project-zot/zot/issues/1591
    - I will rename "IMAGE NAME" to "REPOSITORY" in order to make the header easier to parse
    - The order of the images cannot be predicted if zot is getting them 1 by 1 using the REST API for manifests, so they cannot be sorted when printed. We could wait on all calls to return but that may take minutes, and printing partial results as they become available is better.
    - The order of the images can be predicted when relying on the zot specific search API, but that is not available in all zot servers depending on build options. I added sorting ascending by default. We are planning to implement configurable sorting in a separate PR - see the work under https://github.com/project-zot/zot/pull/1577
    - With regards to the column widths/alignments that was discussed before, and the issue is we don't know the values beforehand for the REST API based responses. As mentioned above printing partial results as they become available is better.
    - The column widths/alignments are partially fixed in this PR for the search API, but we should properly fix this in - see https://github.com/project-zot/zot/pull/851

https://github.com/project-zot/zot/issues/1592
    - Fix missing space after help message

https://github.com/project-zot/zot/issues/1598
    - Fix table headers showing for json/yaml format
    - Fix spacing shown with json format, use 1 row per shown entry in order to be compatible with json lines format: https://jsonlines.org/
    - Add document header `---` to every image shown in yaml format to separate the entries

Signed-off-by: Andrei Aaron <aaaron@luxoft.com>
2023-07-12 10:21:12 -07:00
..
cache refactor(storage): refactoring storage (#1459) 2023-05-26 11:08:19 -07:00
common fix: don't allow blobs to be deleted if in use (#1559) 2023-07-10 12:24:45 +03:00
constants fix: revert "org.opencontainers.referrers.filtersApplied" (#1478) 2023-05-26 13:56:44 -07:00
local fix: don't allow blobs to be deleted if in use (#1559) 2023-07-10 12:24:45 +03:00
s3 fix: don't allow blobs to be deleted if in use (#1559) 2023-07-10 12:24:45 +03:00
types fix(storage): do not open/download blobs when validating manifests (#1566) 2023-07-06 10:33:36 -07:00
cache.go refactor(storage): refactoring storage (#1459) 2023-05-26 11:08:19 -07:00
cache_benchmark_test.go feat(cache): dynamodb implementation (#953) 2022-11-22 10:29:57 -08:00
cache_test.go refactor(cache): rewrote/refactored cachedb functionality to use interface (#667) 2022-11-02 15:53:08 -07:00
README.md refactor(cache): rewrote/refactored cachedb functionality to use interface (#667) 2022-11-02 15:53:08 -07:00
scrub.go feat(cli): Fix multiple issues with zli output (#1612) 2023-07-12 10:21:12 -07:00
scrub_test.go feat(cli): Fix multiple issues with zli output (#1612) 2023-07-12 10:21:12 -07:00
storage.go refactor(storage): refactoring storage (#1459) 2023-05-26 11:08:19 -07:00
storage_controller.go refactor(storage): refactoring storage (#1459) 2023-05-26 11:08:19 -07:00
storage_test.go fix: don't allow blobs to be deleted if in use (#1559) 2023-07-10 12:24:45 +03:00

README.md

zot currently supports two types of underlying filesystems:

  1. local - a locally mounted filesystem

  2. remote - a remote filesystem such as AWS S3

The cache database can be configured independently of storage. Right now, zot supports the following database implementations:

  1. BoltDB - local storage. Set the "cloudCache" field in the config file to false. Example: examples/config-boltdb.json