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/extensions/_zot.md

17 lines
732 B
Markdown
Raw Normal View History

use zot as an extension name, ext as a component and search as a module add endpoints field in ext discover api distribution spec extension discover api has endpoints field required. https://github.com/opencontainers/distribution-spec/blob/main/extensions/_oci.md#extensions-property-descriptions Signed-off-by: Shivam Mishra <shimish2@cisco.com>
2022-05-23 14:22:52 -05:00
`zot` [extension](#references)
===
`zot` extension has following components accessible under `/v2/_zot` endpoint.
Component | Endpoint | Description
--- | --- | ---
[`search`](search/search.md) | `/v2/_zot/ext/search` | efficient and enhanced registry search capabilities using graphQL backend
refactor(extensions)!: refactor the extensions URLs and errors (#1636) BREAKING CHANGE: The functionality provided by the mgmt endpoint has beed redesigned - see details below BREAKING CHANGE: The API keys endpoint has been moved - see details below BREAKING CHANGE: The mgmt extension config has been removed - endpoint is now enabled by having both the search and the ui extensions enabled BREAKING CHANGE: The API keys configuration has been moved from extensions to http>auth>apikey mgmt and imagetrust extensions: - separate the _zot/ext/mgmt into 3 separate endpoints: _zot/ext/auth, _zot/ext/notation, _zot/ext/cosign - signature verification logic is in a separate `imagetrust` extension - better hanling or errors in case of signature uploads: logging and error codes (more 400 and less 500 errors) - add authz on signature uploads (and add a new middleware in common for this purpose) - remove the mgmt extension configuration - it is now enabled if the UI and the search extensions are enabled userprefs estension: - userprefs are enabled if both search and ui extensions are enabled (as opposed to just search) apikey extension is removed and logic moved into the api folder - Move apikeys code out of pkg/extensions and into pkg/api - Remove apikey configuration options from the extensions configuration and move it inside the http auth section - remove the build label apikeys other changes: - move most of the logic adding handlers to the extensions endpoints out of routes.go and into the extensions files. - add warnings in case the users are still using configurations with the obsolete settings for mgmt and api keys - add a new function in the extension package which could be a single point of starting backgroud tasks for all extensions - more clear methods for verifying specific extensions are enabled - fix http methods paired with the UI handlers - rebuild swagger docs Signed-off-by: Andrei Aaron <aaaron@luxoft.com>
2023-08-02 13:58:34 -05:00
[`mgmt`](README_mgmt.md) | `/v2/_zot/ext/mgmt` | config management
[`userprefs`](README_userprefs.md) | `/v2/_zot/ext/userprefs` | change user preferences
[`imagetrust`](README_imagetrust.md) | `/v2/_zot/ext/cosign` | cosign public key management
[`imagetrust`](README_imagetrust.md) | `/v2/_zot/ext/notation` | notation certificate management
use zot as an extension name, ext as a component and search as a module add endpoints field in ext discover api distribution spec extension discover api has endpoints field required. https://github.com/opencontainers/distribution-spec/blob/main/extensions/_oci.md#extensions-property-descriptions Signed-off-by: Shivam Mishra <shimish2@cisco.com>
2022-05-23 14:22:52 -05:00
# References
[1] https://github.com/opencontainers/distribution-spec/tree/main/extensions
Reference in a new issue Copy permalink