Repository navigation
Description
Question
The deployed app reads one nested window.__MINT_CONFIG__ object, written by the container entrypoint at startup from a single generator function. Decide the actual values for TACC's cluster and record them as chart values:
- Hasura GraphQL endpoint — TACC's, not ISI's. Confirm which one their cluster serves and whether it is the same instance the Lit app uses today.
- CKAN —
DATA_CATALOG_APIandDATA_CATALOG_BROWSE_URLas two distinct values (T6 may repoint the first at a proxy path). - OAuth2 — issuer, client id, redirect URI, matching what T5 confirmed.
The Lit app used flat window.REACT_APP_* globals; the two contracts are incompatible, so nothing can be copied across verbatim from the existing deployment.
Deriving these from the other components' ingress declarations is what the chart already does for service endpoints — reuse that rather than hardcoding hostnames where you can.
Sharpened by Commit .env.example and local-setup notes so ui-react runs for someone who is not Max:
the key list is complete, and one key is gone.
That ticket deleted MODEL_CATALOG_API. No code used it. Decide these 12 keys:
HASURA_ENDPOINT · AUTH_SERVER · AUTH_CLIENT_ID · AUTH_PROVIDER · AUTH_REALM ·
GOOGLE_MAPS_KEY · DATA_CATALOG_API · DATA_CATALOG_BROWSE_URL · ENSEMBLE_MANAGER_API ·
AUTH_CALLBACK_ORIGIN · AUTH_PREVIEW_ORIGIN_ALLOWLIST · WELCOME_MESSAGE
Three keys need a decision, not a hostname lookup:
- Set
ENSEMBLE_MANAGER_API.MintThread.tsxreads it. The generator omits the key
when it is unset, so the page can find the absence. If you leave it unset, thread
execution stops without an error. The smoke test in
#76 would show a missing feature, not
a fault. AUTH_PREVIEW_ORIGIN_ALLOWLISTis for Vercel. It corrects a browser origin that
differs from the registered origin. Atmint.tacc.utexas.eduthe two origins are the
same. Leave the key empty. Do not copy it from the Vercel project. See the Check whether the OAuth2 redirect URI for mint.tacc.utexas.edu is already registered #73 block below
forAUTH_CALLBACK_ORIGIN.AUTH_REALMis for Keycloak only. Tapis ignores it.
Read ui-react/.env.example before you decide. It gives each key, its default, and its
behaviour when unset.
Sharpened by Check whether the OAuth2 redirect URI for mint.tacc.utexas.edu is already registered:
the OAuth2 bullet is now settled — these are the values, not a question:
auth:
provider: tapis # chart default already correct
server: https://portals.tapis.io # chart default already correct
components:
ui_react:
config:
client_id: "mint" # the SAME client the Lit app uses
auth_callback_origin: "" # empty = use the deployment's own originmint is the client registered in the Tapis portals tenant with callback_url
exactly https://mint.tacc.utexas.edu/oauth2/callback — which is the string ui-react
sends from that origin, verified live against the IdP. No new client, no IdP change.
charts/mint/values.yaml and the fail in
templates/ui-react-config.yaml insist the React client "must be a client distinct from the
legacy UI's". That reasoning assumes the two apps serve different origins; in this rollout
they share one origin sequentially (Lit is unrouted, per #77), and they want the identical
redirect URI. The template only hard-fails on an empty client_id, so "mint" renders fine.
The host is part of the OAuth contract: Tapis matches redirect_uri on scheme, host and path,
so the ingress must serve exactly https://mint.tacc.utexas.edu — plain http:// is rejected.
Activity
mosoriob commentedon Aug 8, 2026
Answer: set two values. The other ten are already correct.
The deployed Lit app publishes its runtime config at
https://mint.tacc.utexas.edu/config.js.That file is TACC's own truth, not ISI's. Every endpoint below comes from it.
The 12 keys at TACC
mint.tacc.utexas.eduHASURA_ENDPOINThttps://graphql.mint.tacc.utexas.edu/v1/graphqlAUTH_SERVERhttps://portals.tapis.ioAUTH_CLIENT_IDmintclient_idAUTH_PROVIDERtapisAUTH_REALMGOOGLE_MAPS_KEYDATA_CATALOG_APIhttps://ckan.tacc.utexas.edudata_catalog_apiDATA_CATALOG_BROWSE_URLhttps://ckan.tacc.utexas.eduENSEMBLE_MANAGER_APIhttps://ensemble-manager.mint.tacc.utexas.edu/v1AUTH_CALLBACK_ORIGINAUTH_PREVIEW_ORIGIN_ALLOWLISTWELCOME_MESSAGEWelcome to MINTGOOGLE_MAPS_KEYandWELCOME_MESSAGEare top-level chart values shared with the Lit app.The
ui_reacttemplate reads the same two values. TACC's overrides apply automatically.The values to add
Why derivation is safe for Hasura and Ensemble Manager
I did not have to guess whether TACC declares
ingress.tls. The Lit template and themint.component_urlhelper use the same{{ if .ingress.tls }}idiom. Lit's live output showsREACT_APP_GRAPHQL_ENABLE_SSL = trueand anhttps://ensemble manager URL. So both ingressesdeclare TLS, and derivation gives
https://for both. A missing TLS block would have givenhttp://and mixed-content failures. The/v1suffix comes fromapi_version, which Lit'slive URL also confirms.
Why CKAN must be explicit
The
ui_reacttemplate derivesDATA_CATALOG_APIfromcomponents.data_catalog. TACC does notuse that component; it is disabled by default. TACC uses
external_services.ckan.url, whichui-config.yamlreads andui-react-config.yamldoes not. So the key is omitted from theConfigMap and the app falls back to its compiled default. That default is
https://ckan.tacc.utexas.edu— the right value by coincidence. Set it explicitly.Chart debt:
ui-react-config.yamlshould readexternal_services.ckan.url, asui-config.yamldoes. The override makes the fix optional, not urgent.Verified live from the
https://mint.tacc.utexas.eduoriginAccess-Control-Allow-Origin: *. An anonymous query returned a rowfrom
modelcatalog_standard_variable.GET /v1/executions/<id>/logsreturns 404 for an unknown id, so the route exists and the service is live.
X-Frame-Optionsand no CSP. The datasets browse iframe will render.CORS is therefore not a risk for Hasura or the Ensemble Manager. Both send a wildcard to every
origin. Only CKAN uses an allowlist, and #71 settled that.
No CKAN API key is needed → #76
Lit sets
DATA_CATALOG_KEYfrom a chart secret.ui-reacthas no such key and needs none. Itcalls only
package_searchandpackage_show, with GET. Every read is anonymous.Two notes for the flip → #77
MODEL_CATALOG_API. Commit .env.example and local-setup notes so ui-react runs for someone who is not Max #72 deleted that key from the app. Thegenerator ignores unknown variables, so the extra key is harmless. Remove it when convenient.
values.yamland thefailinui-react-config.yamlsay the React client must differ fromLit's. Check whether the OAuth2 redirect URI for mint.tacc.utexas.edu is already registered #73 settled that this is wrong for this rollout. The
failtriggers only on anempty
client_id, so"mint"renders.