1fanwang commented on issue #66804: URL: https://github.com/apache/airflow/issues/66804#issuecomment-4483362672
Fair point — agreed the rate-limiter itself belongs in the gateway, not inside Airflow. Thanks @potiuk for the quick read, and for naming the right shape (expose what the gateway needs rather than reimplement). Closing this. If it'd help in a separate scoped issue, surfacing the JWT-decoded principal in a response header so envoy / nginx can key per-user limits without cracking the token themselves looks like a clean angle to pursue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
