-
Notifications
You must be signed in to change notification settings - Fork 4
Add alternative_endpoints field to GetReportResponse for direct conne… #21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
WalkthroughThe pull request updates the proto definitions in Changes
Poem
Tip ⚡🧪 Multi-step agentic review comment chat (experimental)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
proto/jumpstarter/v1/jumpstarter.proto (1)
133-137: Addition of the Endpoint MessageThe new
Endpointmessage has been defined appropriately with the required fieldsendpointandtoken, and an optional fieldcertificatefor additional data. A minor consideration: in proto3, theoptionalmodifier for scalar types requires explicit support (enabled via a flag) if you need presence tracking. Confirm that your project's protos are configured for this behavior. If not, you may consider removing theoptionalspecifier if presence tracking isn’t needed.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
proto/jumpstarter/v1/jumpstarter.proto(1 hunks)
🔇 Additional comments (1)
proto/jumpstarter/v1/jumpstarter.proto (1)
130-131: Addition of alternative_endpoints Field in GetReportResponseThe new repeated field
alternative_endpointsis correctly appended as field number 4, following the existing fields inGetReportResponse. Ensure that downstream consumers of theGetReportResponseare updated to handle this new field as needed, and that any serialization/deserialization logic properly incorporates this change.
| message Endpoint { | ||
| string endpoint = 1; | ||
| string token = 2; | ||
| optional string certificate = 3; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, since you discover this self-signed cert during connection thorough the main jumpstarter-controller... you know you can trust it. you obtained it in a secure channel :D
And same for the token,
brilliant!
…ctivity
Summary by CodeRabbit