Skip to content

[Backport release/0.0.14] docs(teleop): correct broker key and identity guidance - #4188

Open
github-actions[bot] wants to merge 1 commit into
release/0.0.14from
backport/4087-to-release/0.0.14
Open

github-actions[bot] wants to merge 1 commit into
release/0.0.14from
backport/4087-to-release/0.0.14

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Description

Backport of #4087 to release/0.0.14.

@greptile-apps

greptile-apps Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

RetriggerConfidence Score: 5/5

Safe to merge: the updated environment and documentation match the broker's implemented defaults and optional identity behavior.

What we checked:

  • Ran the offline configuration verifier against the parent and current environment templates using the real hosted blueprint parser and broker configuration constructor. T-Rex
  • The parent environment overrides the broker URL and robot ID, while the current environment leaves both unset, resolving to https://api.dimensional.org and robot_id=None. T-Rex
  • Ran the focused broker credential and optional-identity test successfully (1 passed). T-Rex
  • The verifier source used for this validation is included with the captured outputs. T-Rex
  • For deeper validation, runtime/default and identity contract results were captured in after logs and before/after comparisons, the existing focused identity test shows 1 passed, and the verifier script hosted-broker-config-contract.py was executed. T-Rex

Summary

  • Removes obsolete hosted teleoperation environment overrides so the supported broker endpoint and API-key-derived robot identity apply by default.
  • Updates API-key format and creation guidance across runtime messages, integration guidance, and hosted teleoperation documentation.
  • The configuration path was exercised with the real blueprint parser and broker configuration construction; no issues were found.

Reviews (1) · Last reviewed commit: "docs(teleop): correct broker key and ide..."

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.

2 participants