-
Notifications
You must be signed in to change notification settings - Fork 101
[docs] Update documentation for Artifactory archive entry download (2026-04-05) #579
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -199,6 +199,18 @@ With `PROXY_REGISTRY_ONLY=1`, APM will: | |
| 2. Skip the download cache for entries that have no `registry_prefix` (forcing a fresh proxy download) | ||
| 3. Raise an error for any package reference that does not route through the configured proxy | ||
|
|
||
| ### Archive Entry Download (virtual file packages) | ||
|
|
||
| When downloading virtual file packages (`.prompt.md`, `.agent.md`, and similar single-file primitives) through an Artifactory proxy, APM uses the **Archive Entry Download API** to fetch only the specific file instead of the full archive. | ||
|
|
||
| The entry URL follows the Artifactory pattern: | ||
|
|
||
| ``` | ||
| GET {archive_url}!/{repo}-{ref}/{file_path} | ||
| ``` | ||
|
|
||
| This avoids downloading a multi-MB archive just to extract a single small file. If the entry API returns a 404, a connection error, or is unsupported by the Artifactory version in use, APM falls back to the standard full-archive download transparently -- no configuration required. | ||
|
|
||
|
Comment on lines
+202
to
+213
|
||
| ### Deprecated Artifactory env vars | ||
|
|
||
| The following env vars still work but emit a `DeprecationWarning`. Migrate to the `PROXY_REGISTRY_*` equivalents: | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
[Unreleased]section now includes an entry for feature PR #525, but the changelog already documents #525 under the released0.8.10section (and with a different category:Changed). This will cause duplicate/misleading release notes. Consider removing this new Unreleased entry; if the intent is to track this documentation-only PR, add a concise entry that references this PR number instead of #525.