Skip to content

docs(extensibility): name extension base capabilities - #4405

Open
ericcurtin wants to merge 1 commit into
NVIDIA:mainfrom
ericcurtin:docs/4378-extension-base-capability/ericcurtin
Open

ericcurtin wants to merge 1 commit into
NVIDIA:mainfrom
ericcurtin:docs/4378-extension-base-capability/ericcurtin

Conversation

@ericcurtin

Copy link
Copy Markdown
Contributor

Summary

Name the base capability each extension family must declare.

Related Issue

Closes #4378

Changes

  • Docs: table of base capabilities with an example manifest.
  • Proto: name the expected values next to each extension field.
  • Missing metadata and missing version errors now name the expected protocol and capability.

Testing

  • Checks appropriate to the affected code and behavior pass
  • Unit tests added/updated (if applicable)
  • E2E tests added/updated (if applicable)

cargo fmt, cargo clippy and cargo test for openshell-core. mise run docs passes.

Checklist

  • Follows Conventional Commits
  • Commits are signed off (DCO)
  • Architecture docs updated (if applicable)

Signed-off-by: Eric Curtin <eric.curtin@docker.com>
@copy-pr-bot

copy-pr-bot Bot commented Oct 11, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@ericcurtin

Copy link
Copy Markdown
Contributor Author

@johntmyers @elezar PTAL when you get a chance, and /ok to test 0bf47e0f89e757c31837d4a1ced86fb4c10f90eb if it looks good. Thank you!

This branch has not been deployed

No deployments
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.

bug(docs): supervisor middleware docs no longer name the base capability that Describe must return

1 participant