holger-artifactory-connector — crate card
Reverse-engineered (from source — verify, don't trust the name)
- One-line pitch: Agent connector for JFrog Artifactory — the Artifactory twin of the Nexus connector, same
ConnectorTrait. - Does: Implements
ConnectorTraitover Artifactory REST + AQL: list repos (GET /api/repositories), list assets (POST /api/search/aqlitems.find, building download URLs from base+repo/path/name), download (GET /<repo>/<path>/<name>), upload/deploy (PUT /<repo>/<path>). Auth mirrors Nexus (Basic / OIDC-or-access-token Bearer / mTLS / None) with the same SSRF / credential-exfiltration guard (credentials only on same-origin URLs) andread_cappedbody caps (8 GiB download, 256 MiB JSON). - Key deps:
traits,async-trait,reqwest(rustls-tls, json),serde/serde_json,log. - Shape: lib, single
lib.rs. - Observed role in the workspace: The third connector re-exported by
holger-agent-lib; enables the agent's--to artifactory/ suck-from-artifactory path (wired through holger-airgap'slib/push.sh).
Fill in (one line each — only the human knows these)
- Primary consumer(s):
- Why it exists (vs the obvious alternative):
- Hard constraint (airgap / no-C-deps / no-FFI / pure-Rust / etc.):
- Release cadence & independence (rides a parent? own repo someday?):
- Status (production / prototype / experimental / stubbed):
- Must-NOT-change invariant:
- Biggest known gap or TODO:
- Anything a newcomer would get wrong about it: