NVIDIA / NVIDIA/nvidia-oci-samples

Duplicate AIQ and RAG samples after the use-case restructure

Open
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
2
Forks
8
Avg merge
3d 5h
Merged PRs (30d)
7

Description

After the reorganization in #14 and #15, two samples exist as full copies under both agentic/ and industry-solutions/:

  • agentic/oke/aiq/aiq-2.0 and industry-solutions/oke/aiq/aiq-2.0 are byte-identical except for the cd path in the README and one trailing newline in deploy/terraform/modules/network/main.tf. The root README links both copies under "Agentic" and "Industry Solutions".
  • agentic/oke/rag and industry-solutions/oke/rag are byte-identical. Neither copy is linked from the root README.

Keeping two full copies means they will drift (the Terraform module already differs by a line), and the same fix has to be made twice.

Suggested fix, whichever you prefer:

  1. Keep one canonical copy (say under agentic/, since AIQ and RAG are agentic patterns) and, if you still want them discoverable under Industry Solutions, replace the second copy with a short README that links to the canonical one, or just cross-link from the root README.
  2. Point both root-README entries at the single canonical path.

Happy to send the PR once you decide which location should be canonical; didn't want to delete a directory from the restructure without your call.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the root README and compare the paired paths agentic/oke/aiq/aiq-2.0, industry-solutions/oke/aiq/aiq-2.0, agentic/oke/rag, and industry-solutions/oke/rag. Confirm the maintainer's canonical location before changing anything; done means one full copy remains, duplicate links or directories are replaced with links as decided, and the Terraform files no longer drift.

Written by the indexing model from the issue text.

Assessment

Tech stack
terraform
Domain
documentation, infrastructure
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.