Skip to content

Develop#44

Merged
divyasinghds merged 2 commits into
mainfrom
develop
May 21, 2026
Merged

Develop#44
divyasinghds merged 2 commits into
mainfrom
develop

Conversation

@divyasinghds
Copy link
Copy Markdown
Contributor

@divyasinghds divyasinghds commented May 21, 2026

Summary

Related

Type of change

  • Feature
  • Bug fix
  • Tech-debt / refactor
  • Docs
  • Security / hardening
  • Breaking change

Test plan

Screenshots / recordings

Deployment notes

Checklist

  • Tests added / updated and passing locally
  • Docs updated if behavior or config changed
  • No secrets / credentials in the diff
  • For security-sensitive paths: appropriate reviewer requested

Note

Low Risk
Low risk documentation-only changes that don’t affect runtime behavior; risk is limited to users following updated Helm commands and ingestion steps.

Overview
Adds a new recommended declarative ingestion path to prepare-dataset.mdx, documenting ingest.yaml + helm install tracebloc/ingestor, required data staging on the shared PVC, and links to per-category examples/README.

Clarifies the existing advanced flow as the fallback option and adds an explicit helm upgrade ... --reset-then-reuse-values note to setup-guide.mdx for one-liner installs.

Reviewed by Cursor Bugbot for commit aa81c24. Bugbot is set up for automated code reviews on this repo. Configure here.

saadqbal and others added 2 commits May 18, 2026 13:54
docs: clarify setup guide deploys single-node workspace
…43)

Two changes to the prepare-data and setup-guide pages driven by user
feedback after a fresh end-to-end setup:

- prepare-dataset.mdx: lead with the declarative YAML method (helm
  install tracebloc/ingestor --set-file ingestConfig=./ingest.yaml).
  The existing Python-template + Docker + kubectl flow stays as the
  advanced path for users who need custom processors. Calls out that
  ingest.yaml fields vary per category and points at the per-category
  examples in the data-ingestors repo.
- setup-guide.mdx: add a Note after the curl one-liner pointing at
  the helm upgrade command (--reset-then-reuse-values, --version) so
  users know how to upgrade an installer-deployed client without
  losing applied values.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@LukasWodka
Copy link
Copy Markdown
Contributor

👋 Heads-up — Code review queue is at 18 / 8

Above the WIP limit. The team convention is to review existing PRs before opening new work.

Open PRs currently in Code review (oldest first):

Pull from review before opening new work. (This is a nudge from the kanban WIP check, not a block.)

@divyasinghds divyasinghds merged commit 4399c45 into main May 21, 2026
8 of 9 checks passed
@divyasinghds divyasinghds deleted the develop branch May 21, 2026 12:30
@divyasinghds divyasinghds restored the develop branch May 21, 2026 12:30
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.

4 participants