Expected Behavior

Feast UI’s cURL Generator should use the actual Feature Server endpoint configured by the user (e.g. from feature_store.yaml, CLI flags, or an environment variable), instead of always defaulting to:

http://localhost:6566

Users running Feast in Kubernetes, Docker, or remote environments should get a correct, usable curl command from the UI.

Current Behavior

The cURL Generator in Feast UI always hard-codes the Feature Server URL to:

http://localhost:6566

This happens even when:

• The feature server is running remotely
• The UI is accessed from a browser not running on the same host
• A custom serving URL is configured elsewhere

There is currently no flag, config, or environment variable to override this value when running:

feast ui

This makes the generated cURL snippet incorrect and misleading in non-local setups.

Steps to reproduce

1. Deploy Feast Feature Server remotely (e.g. Kubernetes or Docker).

2. Run the UI:

   feast ui

3. Open the UI in a browser.

4. Go to Feature Views → Curl Generator.

5. Observe the generated command:

   curl http://localhost:6566/get-online-features

6. Run this from your local machine → it fails because the server is not local.

Specifications

• Version: 0.57.0
• Platform: Kubernetes
• Subsystem: Feast UI (CurlGeneratorTab.tsx)

Possible Solution

• Allow the Feature Server base URL to be configurable via:

  • Environment variable (e.g. FEAST_FEATURE_SERVER_URL)
  • feature_store.yaml

Example approach:

const FEAST_FEATURE_SERVER_URL =
  process.env.REACT_APP_FEAST_FEATURE_SERVER_URL ??
  "http://localhost:6566";

This would make the cURL generator usable in real production deployments.