René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Migrate Feast UI to Use REST API Registry Server","articleBody":"**Summary** :\n\nThis is about proposing migrating the Feast UI to use the new REST API-based registry server as the primary data source instead of relying on the protobuf-serialized registry. \n\nThis migration will improve projects isolation, RBAC, production-grade deployments of Feast and will pave the way for a more flexible and secure UI architecture.\n\nGoals can be :\n\n- Fetch registry data via the REST API endpoints scoped by project.\n- Eliminate dependency on serialized registry protos.\n- Improve support for RBAC authenticated and authorized user access.\n- Lay the foundation for future UI-driven create, update, and delete functionality.\n\nThis can be done by:\n- Change FastAPI() https://github.com/feast-dev/feast/blob/master/sdk/python/feast/ui_server.py#L20 to use RestRegistryServer https://github.com/feast-dev/feast/blob/master/sdk/python/feast/api/registry/rest/rest_registry_server.py#L26 \n- Modify [useLoadRegistry.ts](https://github.com/feast-dev/feast/blob/master/ui/src/queries/useLoadRegistry.ts) and [useLoadRelationshipsData.ts](https://github.com/feast-dev/feast/blob/master/ui/src/queries/useLoadRelationshipsData.ts) to use project name and registry rest-api server url\n- Modify pages  ","author":{"url":"https://github.com/ntkathole","@type":"Person","name":"ntkathole"},"datePublished":"2025-06-02T05:57:55.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/5411/feast/issues/5411"}