Skip to content

docs: update README for OCI with sidecar#97

Merged
julpayne merged 2 commits intoeval-hub:mainfrom
tarilabs:tarilabs-20260327-docs
Mar 27, 2026
Merged

docs: update README for OCI with sidecar#97
julpayne merged 2 commits intoeval-hub:mainfrom
tarilabs:tarilabs-20260327-docs

Conversation

@tarilabs
Copy link
Copy Markdown
Member

@tarilabs tarilabs commented Mar 27, 2026

now OCI Artifact Push goes through sidecar for Authentication

What and why

Closes #

Type

  • feat
  • fix
  • docs
  • refactor / chore
  • test / ci

Testing

  • Tests added or updated
  • Tested manually

Breaking changes

Summary by CodeRabbit

  • Documentation
    • Updated architecture diagram to show a sidecar-based, authenticated push of OCI artifacts to the registry.
    • Revised OCI Artifact Persistence docs: removed the proof-of-concept note and the advanced direct-persistence section.
    • Updated examples and the benchmark snippet to use adapter-driven configuration and the adapter-based job spec.
    • Clarified OCI artifact behavior for Kubernetes mode to describe sidecar-authenticated registry pushing.

now OCI Artifact Push goes through sidecar for Authentication

Signed-off-by: tarilabs <matteo.mortari@gmail.com>
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 27, 2026

📝 Walkthrough

Walkthrough

Updated README.md: the architecture diagram now inserts a dedicated sidecar step (S3) between the adapter callback and the OCI Registry, and documentation/code snippets were revised to use adapter-driven callback construction and adapter job spec for benchmarking; removed direct persister examples.

Changes

Cohort / File(s) Summary
Documentation
README.md
Reworked Mermaid architecture diagram to add an S3 sidecar for authenticated OCI artifact pushes (A4 --> S3, S3 --> Registry), replaced manual DefaultCallbacks(...) construction with DefaultCallbacks.from_adapter(adapter), switched benchmark example to adapter.job_spec, and removed direct persister usage examples.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I hopped through the diagram, tip-tap on the log,
A little S3 sidecar joined our registry jog,
Callbacks now guided by the adapter's song,
Benchmarks point to job_spec all along,
Pushing artifacts snug, steady, and strong. 🥕✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: updating README documentation to reflect OCI artifact push now routing through a sidecar for authentication.
Description check ✅ Passed The description follows the required template with all essential sections completed: 'What and why' provided, Type marked as 'docs', Testing section present, and Breaking changes section included.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Line 37: Update the S3 node label S3["Authenticated Push OCI artifacts
to<br/>OCI Registry"] to a clearer, consistent noun- or verb-phrase (e.g.,
"Authenticated OCI Artifact Push" or "Push OCI Artifacts (Authenticated)") so
the diagram reads cleanly; replace the current awkward sentence with one of
these concise label forms and preserve the HTML line break if needed for layout.
- Around line 43-48: The architecture diagram now shows OCI artifact pushes
routed via the sidecar (nodes A4 -> S3, A5 -> S4 and edges S2 -> EvalHub, S3 ->
Registry), but the README prose in the "Key Points" section still states the SDK
pushes artifacts directly; update that prose and any examples to say the SDK
performs pushes through the sidecar sidecar component (EvalHub/sidecar) to the
OCI Registry instead of direct SDK-to-Registry pushes, adjust example
commands/snippets and any configuration guidance to reference the sidecar
endpoint (EvalHub) and sidecar flow, and ensure references to symbols like
EvalHub, Registry, S3/S4/A4/A5 align with the diagram language used elsewhere.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 107dbdb0-0433-48da-a5b1-fe0fdee7b0f8

📥 Commits

Reviewing files that changed from the base of the PR and between 82ad9bd and 15a4536.

📒 Files selected for processing (1)
  • README.md

Signed-off-by: tarilabs <matteo.mortari@gmail.com>
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

♻️ Duplicate comments (1)
README.md (1)

185-198: ⚠️ Potential issue | 🟠 Major

README still has stale callback examples that conflict with this new canonical path.

This section correctly promotes DefaultCallbacks.from_adapter(adapter), but later snippets still show direct DefaultCallbacks(...) usage with unsupported params (registry_url, registry_username, registry_password) and job_spec.job_id instead of job_spec.id. That makes the README internally inconsistent and can lead users to broken integration code.

Suggested doc alignment (replace stale direct-construction snippets)
-# Create callbacks
-callbacks = DefaultCallbacks(
-    job_id=job_spec.job_id,
-    benchmark_id=job_spec.benchmark_id,
-    benchmark_index=job_spec.benchmark_index,
-    sidecar_url=job_spec.callback_url,
-    registry_url=settings.registry_url,
-    registry_username=settings.registry_username,
-    registry_password=settings.registry_password,
-    insecure=settings.registry_insecure,
-)
+# Create callbacks from adapter (recommended)
+callbacks = DefaultCallbacks.from_adapter(adapter)
-# Run adapter
-results = adapter.run_benchmark_job(job_spec, callbacks)
+# Run adapter
+results = adapter.run_benchmark_job(adapter.job_spec, callbacks)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 185 - 198, The README contains stale examples that
instantiate DefaultCallbacks directly with unsupported parameters and use
job_spec.job_id; update the examples to use
DefaultCallbacks.from_adapter(adapter) (referencing
DefaultCallbacks.from_adapter and adapter) instead of direct
DefaultCallbacks(...) and remove any unsupported args like registry_url,
registry_username, registry_password; also replace job_spec.job_id occurrences
with job_spec.id so the snippets match the current API and the new canonical
usage.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@README.md`:
- Around line 185-198: The README contains stale examples that instantiate
DefaultCallbacks directly with unsupported parameters and use job_spec.job_id;
update the examples to use DefaultCallbacks.from_adapter(adapter) (referencing
DefaultCallbacks.from_adapter and adapter) instead of direct
DefaultCallbacks(...) and remove any unsupported args like registry_url,
registry_username, registry_password; also replace job_spec.job_id occurrences
with job_spec.id so the snippets match the current API and the new canonical
usage.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a7adfc6d-0b80-4e97-8467-dd57933ee89c

📥 Commits

Reviewing files that changed from the base of the PR and between 15a4536 and c8d1e66.

📒 Files selected for processing (1)
  • README.md

@julpayne julpayne merged commit 6539586 into eval-hub:main Mar 27, 2026
9 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Apr 1, 2026
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants