Skip to content

Document machine-wide resource name uniqueness - #5460

Open
Jeremy Rose (jeremyrose-viam) wants to merge 2 commits into
viamrobotics:mainfrom
jeremyrose-viam:worktree-resource-name-uniqueness-docs
Open

Jeremy Rose (jeremyrose-viam) wants to merge 2 commits into
viamrobotics:mainfrom
jeremyrose-viam:worktree-resource-name-uniqueness-docs

Conversation

@jeremyrose-viam

Copy link
Copy Markdown
Member

Documents the viam-server contract that component and service names must be unique across the whole machine, even across different APIs. Shipped in RDK v1.6.0 (rdk PR 6350, RSDK-14326). Closes DOCS-4939.

  • docs/hardware/configure-hardware.md: new "Resource names" subsection under step 2. States the uniqueness rule, that it includes remote and fragment resources, that builtin is reserved for the default services, and what happens on a collision (local resources are not built along with their dependents; a local resource wins over a remote one, which is hidden).
  • docs/hardware/machine-configuration.md: the name field row says unique across the machine and links to the subsection.
  • docs/hardware/multi-machine/add-a-remote-part.md and overview.md: explain that colliding remote resources are hidden and that a prefix prevents it.
  • docs/monitor/troubleshoot.md: tells readers with a missing resource to search the logs for name collision.

Pre-PR checks (prettier 3.2.5, markdownlint, vale 3.16.0 locally, frontmatter_rules.py, make build-prod) passed before merging current main.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@netlify

netlify Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for viam-docs ready!

Name Link
🔨 Latest commit 1ea7bb1
🔍 Latest deploy log https://app.netlify.com/projects/viam-docs/deploys/6adbcf88dd0906e298cfc3a7
😎 Deploy Preview https://deploy-preview-5460--viam-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 34 (no change from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 92 (no change from production)
PWA: 60 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@viambot viambot added the safe to build This pull request is marked safe to build from a trusted zone label Oct 23, 2026

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

safe to build This pull request is marked safe to build from a trusted zone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants