bridge: require registration token for broker registration#111
Merged
Conversation
Greptile SummaryThis PR removes the legacy Key changes:
Confidence Score: 5/5
Important Files Changed
Last reviewed commit: 6ba9064 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
--registration-tokenforbaudbot broker register--auth-codeparsing and payload support frombin/broker-register.mjsbin/baudbotREADME.mdCONFIGURATION.mdAGENTS.mddocs/operations.mdWhy
modem-dev/baudbot-servicesmerged the dashboard-canonical registration flow and/api/registernow requiresregistration_tokenin the primary path. Keepingauth_codein baudbot caused stale UX/docs and a misleading CLI contract.Testing
node --test bin/broker-register.test.mjsnode --check bin/broker-register.mjsbash -n bin/baudbot