#3482 [BUG] flytekit should support the flytectl config.yaml "admin.clientSecretEnvVar" option Issue created by cosmicBboy ### Describe the bug For context,

pyflyte run

and

pyflyte register

use the flytectl config.yaml file for various configuration settings, including client credential secret. The purpose of this issue is to support the

clientSecretEnvVar

key, which reads the credential from the specified environment variable.

admin:
  endpoint: dns:///<your-org.hosted.unionai.cloud>
  clientId: <client-id-from-app-creation>
  # If the secret will be mounted as a file:
  clientSecretLocation: /home/.../<ci-secret>
  # Or, if the secret will be mounted as an environment variable
  clientSecretEnvVar: <env-var>
logger:
  # Logger settings to control logger output. Useful to debug logger:
  show-source: true
  level: 1

Currently, flytekit supports the

clientSecretLocation

key, but not the `clientSecretEnvVar`: https://github.com/flyteorg/flytekit/blob/master/flytekit/configuration/__init__.py#L401-L411 ### Steps: • Support reading

admin.clientSecretEnvVar

into the platform config • If

clientSecretLocation

or

clientSecretEnvVar

is set, automatically set

auth_mode

to

clientSecret

(this is so we match the UnionCloud behavior, see here) ### Expected behavior client-secret-based authentication should work with

admin.clientSecretEnvVar

in the flytectl config.yaml ### Additional context to reproduce No response ### Screenshots No response ### Are you sure this issue hasn't been raised already? • Yes ### Have you read the Code of Conduct? • Yes flyteorg/flyte