Update docs for Resource.Reconfigure removal [On Hold until Next RDK Release]

[Shannon Bradshaw (shannonbradshaw)]

Source changes

• [APP-16062] Reland Remove-Reconfigure + cascade fix consolidation rdk#6098: Reland removal of Reconfigure from the Resource interface. Modular resources are now always rebuilt (Close + construct) on config change. ReconfigureResource RPC is deprecated. Python SDK Reconfigurable protocol is deprecated.

Docs changes

• docs/build-modules/module-reference.md: Go column in the defaults table no longer says "Implement Reconfigure()" — now says "Not supported for modular resources" to match the Python column. ReconfigureResource RPC marked as deprecated with explanation that viam-server now uses RemoveResource + AddResource instead.
• docs/build-modules/platform-apis.md: Fix frontmatter description from "validate and reconfigure functions" to "validate function and constructor".
• docs/data/filter-at-the-edge.md: Change "reconfigure method" to "constructor" when describing how to access dependencies.
• docs/tutorials/configure/pet-photographer.md: Rename Go Reconfigure to private reconfigure since it is no longer part of the public Resource interface.

How I found these

• Xref lookup: search-patterns.yaml entry for Resource.Reconfigure with associated terms (AlwaysRebuild, ReconfigureResource, etc.)
• Grep matches: Full sweep for Reconfigure, reconfigure method, reconfigure function across docs repo
• Prior PRs Update module authoring docs for reconfigure removal #5001 and Sweep module-reference and module-anatomy for reconfigure removal #5002 addressed most references but left these residual items

---

Generated by daily docs change agent

---

Generated by Claude Code

[netlify]

✅ Deploy Preview for viam-docs ready!

Name	Link
🔨 Latest commit	ac86ee4
🔍 Latest deploy log	https://app.netlify.com/projects/viam-docs/deploys/6a43ce366b7ac5000854cd4b
😎 Deploy Preview	https://deploy-preview-5111--viam-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 42 (no change from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 92 (no change from production) PWA: 70 (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.

[btshrewsbury-viam]

Overlaps with #5042 — these should be consolidated. Both PRs rewrite the same module-reference.md defaults table and the same ReconfigureResource RPC row for the same Reconfigure removal (rdk #5944 / reland #6098), with conflicting wording and different base-table states. They can't both merge cleanly; recommend folding into one PR and closing the other.

The release gate isn't met yet. As of June 30, latest rdk release is still v0.132.0 (June 23), which still has Reconfigure in the Resource interface (resource.go@v0.132.0:77); #6098 is 12 commits after that tag. Keep both on hold until v0.133.0 is tagged AND contains #6098 — this PR's "[On Hold until Next RDK Release]" framing is the correct one. Merging before then makes the docs wrong for the current shipped SDK.

If reconciling: this PR covers more files (platform-apis, filter-at-the-edge, pet-photographer) and has the more accurate ReconfigureResource description — on main, viam-server no longer calls ReconfigureResource; it uses RemoveResource + AddResource (no call site remains in module/modmanager/manager.go). Prefer #5042's table treatment though: dropping the in-place row and stating "always rebuilds; not supported in any language" in prose is cleaner than a "Not supported" row. Two fixes for this PR: (1) module.proto has no [deprecated = true] on ReconfigureResource, so phrase it as "no longer called by viam-server" rather than "Deprecated."; (2) the pet-photographer.md code change won't compile on the current released SDK — colorFilterCam embeds only resource.Named, so removing the public Reconfigure leaves it without that interface method (would need resource.AlwaysRebuild embedded). That resolves itself once the removal ships, but confirm against v0.133.0.

[Shannon Bradshaw (shannonbradshaw)]

Good catches on all three points — agreed.

1. Overlap with Update docs for Resource.Reconfigure removal [On Hold until v0.133.0] #5042: This PR was created from a backlog item that didn't track Update docs for Resource.Reconfigure removal [On Hold until v0.133.0] #5042's existence (the earlier PR was opened from a different session). They should be consolidated into one PR. This PR covers more files (platform-apis, filter-at-the-edge, pet-photographer) while Update docs for Resource.Reconfigure removal [On Hold until v0.133.0] #5042 covers the sensor override file and has the cleaner table treatment. I'll defer to your judgment on which to fold into which.

2. Release gate: Correct — rdk#6098 hasn't shipped in a tagged release yet. Putting this on hold until v0.133.0 contains the removal is the right call.

3. Specific fixes when reconciling:

   • Will change _Deprecated._ to "no longer called by viam-server" since the proto doesn't carry [deprecated = true].
   • The pet-photographer.md Reconfigure → reconfigure rename should wait for the release that removes it from the interface, as noted.

Marking this on hold. Happy to close this in favor of folding the additional file coverage into #5042, or vice versa — whichever is easier for you.

---

Generated by Claude Code

[viamrobotics-overwatch]

Hey Shannon Bradshaw (@shannonbradshaw) — CI is green and no reviewer is assigned yet. Could you request one when you have a chance?

Auto-comment from overwatch. Will not re-nudge for 7 days.