Skip to content

Orion Internal Sync: custom http headers #46

Merged
kmesh-bot merged 1 commit intokmesh-net:mainfrom
awgn:orion-internal-sync-http-headers
Aug 27, 2025
Merged

Orion Internal Sync: custom http headers #46
kmesh-bot merged 1 commit intokmesh-net:mainfrom
awgn:orion-internal-sync-http-headers

Conversation

@awgn
Copy link
Contributor

@awgn awgn commented Aug 25, 2025

This PR introduces custom HTTP headers, which will be used consistently across the project in upcoming PRs.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @awgn, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new Rust crate, orion-http-header, designed to centralize and standardize the definition of custom HTTP header names within the project. The primary goal is to ensure consistent usage of these headers across various components, particularly for concerns like tracing, rate-limiting, and proxy-related information. This foundational change prepares the codebase for upcoming features that will rely on these standardized header definitions.

Highlights

  • New Crate Creation: A new Rust crate named orion-http-header has been added to the project, serving as a centralized location for defining HTTP header constants.
  • Macro for Header Definition: A custom_header! macro has been introduced to streamline the creation of http::HeaderName constants, ensuring consistency and reducing boilerplate when defining new headers.
  • Standardized HTTP Header Constants: The new crate defines a set of widely used HTTP header constants, including those for tracing (e.g., B3, Datadog, Traceparent), proxy interactions (e.g., Envoy-specific headers), and custom Orion-specific rate-limiting headers, promoting consistent usage across the project.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new crate orion-http-header to centralize the definition of custom HTTP headers for the project. The implementation uses a macro to create http::HeaderName constants from static strings, which is efficient and type-safe. My main feedback is to enhance the macro to support documentation comments. This will improve the maintainability and usability of the new crate by allowing each header constant to be documented with its purpose, which is crucial for a shared library.

@awgn awgn changed the title Orion sync: custom http headers Orion Internal Sync: custom http headers Aug 26, 2025
@awgn awgn force-pushed the orion-internal-sync-http-headers branch 2 times, most recently from a657100 to 7652f70 Compare August 26, 2025 12:49
@awgn awgn force-pushed the orion-internal-sync-http-headers branch 2 times, most recently from 6a3c41d to 2cc3262 Compare August 26, 2025 12:52
… project

Signed-off-by: Nicola Bonelli <nicola.bonelli@huawei-partners.com>
@awgn awgn force-pushed the orion-internal-sync-http-headers branch from 2cc3262 to 92d7798 Compare August 26, 2025 12:54
@hzxuzhonghu
Copy link
Member

/lgtm

@hzxuzhonghu
Copy link
Member

/approve

@kmesh-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hzxuzhonghu

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kmesh-bot kmesh-bot merged commit c506975 into kmesh-net:main Aug 27, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants