Add metadata to generated CDI specs to indicate how the spec was generated

Open
  • Is something wrong?
#1,226 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@bhaskargurram-ai is already working on this.

Since Oct 15, 2026.

  • #2145 by @bhaskargurram-ai — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
32/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
tooling

Research direction

Start by locating the code path that generates CDI specs and review how spec-level annotations affect the CDI version. Define metadata that records how each spec was generated while preserving the intended CDI compatibility, then verify the generated spec output and its version.

Written by the indexing model from the issue text.

Description

feature help-wanted needs-triage

Ideally we want to include metadata in the generated CDI spec that includes information on how a specific CDI spec was generated. Using spec-level annotations could make sense, but would generate a v0.6.0 spec instead of a v0.5.0 spec.

Dominant language
Go
Stars
4.6k
Forks
609
Avg merge
3d 12h
Merged PRs (30d)
36

Getting set up

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.

More from NVIDIA/nvidia-container-toolkit

All issues in NVIDIA/nvidia-container-toolkit

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.