<#1000 forward api_key to per-cluster DataProxy se...
# flyte-github
a
#1000 forward api_key to per-cluster DataProxy session Pull request opened by dansola • Bug:
ClusterAwareDataProxy._select_and_build
creates a new
SessionConfig
for the per-cluster DataProxy endpoint but doesn't carry over the original session's auth credentials. • Impact: All non-interactive auth (CI/CD using
FLYTE_API_KEY
) silently falls back to PKCE on image builder uploads → hangs waiting for browser. Works locally only because macOS Keychain caches a token from prior PKCE sessions. • Repro:
FLYTE_API_KEY=...
flyte deploy --copy-style none ...
on a Linux runner with no keyring backend. • Fix: Persist the api_key on
SessionConfig
and forward it when creating a new session for a different endpoint. flyteorg/flyte-sdk