You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes. I can contribute a fix for this bug independently.
Feature Request Proposal
Right now, if user deploys deploys Feathr with RBAC disabled, there are still login prompts when user accesses web UI. The means the RBAC flag only works on server side but not on UI side. This causes many confusions.
A proposed change to improve UI experience is make UI respect rbacEnabled env setting set by deployment, only trigger login flow if this flag is true.
Motivation
What is the use case for this feature?
For users who is working on dev/test or evaluation poc, they would prefer to setup a sandbox environment without RBAC to get started quickly.
Details
No response
What component(s) does this feature request affect?
Python Client: This is the client users use to interact with most of our API. Mostly written in Python.
Computation Engine: The computation engine that execute the actual feature join and generation work. Mostly in Scala and Spark.
Feature Registry API: The frontend API layer supports SQL, Purview(Atlas) as storage. The API layer is in Python(FAST API)
Feature Registry Web UI: The Web UI for feature registry. Written in React
The text was updated successfully, but these errors were encountered:
Willingness to contribute
Yes. I can contribute a fix for this bug independently.
Feature Request Proposal
Right now, if user deploys deploys Feathr with RBAC disabled, there are still login prompts when user accesses web UI. The means the RBAC flag only works on server side but not on UI side. This causes many confusions.
A proposed change to improve UI experience is make UI respect rbacEnabled env setting set by deployment, only trigger login flow if this flag is true.
Motivation
For users who is working on dev/test or evaluation poc, they would prefer to setup a sandbox environment without RBAC to get started quickly.
Details
No response
What component(s) does this feature request affect?
Python Client
: This is the client users use to interact with most of our API. Mostly written in Python.Computation Engine
: The computation engine that execute the actual feature join and generation work. Mostly in Scala and Spark.Feature Registry API
: The frontend API layer supports SQL, Purview(Atlas) as storage. The API layer is in Python(FAST API)Feature Registry Web UI
: The Web UI for feature registry. Written in ReactThe text was updated successfully, but these errors were encountered: