Skip to content

feat: register_device tags + preserve tags on rename (HUB-6087) - #51

Merged
danielr-hubblenetwork merged 1 commit into
mainfrom
hub-6087-sat-tags
Aug 25, 2026
Merged

feat: register_device tags + preserve tags on rename (HUB-6087)#51
danielr-hubblenetwork merged 1 commit into
mainfrom
hub-6087-sat-tags

Conversation

@danielr-hubblenetwork

@danielr-hubblenetwork danielr-hubblenetwork commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add optional tags to Organization.register_device / cloud.register_device, sent as the Cloud API’s per-device tags list (tags: [{...}]).
  • Stop sending empty set_tags: {} on name-only update_device / set_device_name. set_tags is a full replace; the empty map was wiping tags applied at registration (needed for satellite FTUE).
  • Unit tests cover both behaviors.

Enables hubble-tldm to register *_sat boards with satellite: next-pass (HUB-6087).

Merge / release notes

  1. Merge this PR.
  2. Cut a 0.14.0 release (new optional API + bugfix) before relying on the companion hubble-tldm PR in production.
  3. Then merge the hubble-tldm PR that passes tags= for _sat boards.

Test plan

  • pytest tests/test_register_device_cloud.py tests/test_register_device_validation.py
  • After release: register a device with tags={"satellite": "next-pass"}, then set_device_name, and confirm tags remain on GET device

Made with Cursor

Allow custom tags at registration time for FTUE satellite boards, and omit
empty set_tags on name-only updates so those tags are not replaced.

Co-authored-by: Cursor <cursoragent@cursor.com>
@danielr-hubblenetwork
danielr-hubblenetwork merged commit 3f4d309 into main Aug 25, 2026
2 checks passed
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