You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@texera.apache.org by "aicam (via GitHub)" <gi...@apache.org> on 2025/10/14 18:16:24 UTC

[I] Add dynamic router to local development [texera]

aicam opened a new issue, #3901:
URL: https://github.com/apache/texera/issues/3901

   ## Issue
   
   - Currently, access control service is only used in Kubernetes, therefore, developers who add features to local development environment can not test their feature unless they run Kubernetes.
   - We have two logics for authorizing requests which make our development inconsistent, in other words, a feature developed on local development mode may not work correctly on Kubernetes.
   
   ## Current router in local development
   In our local development when there is no Kubernetes and Envoy service, we use simple Angular routing. It has a static routing mechanism where requests are redirected to a specific service based on their path.
   
   ## Solution
   We need to find a way to use a dynamic routing system in local development. Technically, we need Envoy service but without need to run it on Kubernetes and can be ran locally.


-- 
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: dev-unsubscribe@texera.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org