#1099

Apologies for after-the-fact commentary - but I have tested this and it works. For the benefit of others who might stumble across this (and for the authors and maintainers) - the use of the env var in static client config is different that the use of env var in other areas of the same config file. for example, in configuring the google connector - you'd do this:

  config:
    clientID: $GOOGLE_CLIENT_ID
    clientSecret: $GOOGLE_CLIENT_SECRET**

Later - in the same configmap, to ref "secretEnv" - you'd do this:

staticClients:
- id: kubelogin
  redirectURIs:
  - http://localhost:28000
  name: 'kubelogin'
  secretEnv: KUBELOGIN_SECRET

Note - no $ before the env var ref, when (by convention) the variable name ends in Env.

I've built from source, and can confirm this does work. Ultimately i'd love to see more consistency in the use of env vars across the configmap yaml, but I do appreciate everyone's work. This was a blocker for me - as of yesterday, and found your PR today. thanks !

@paul-theorem you can see #1428 (comment) for an explanation of the inconsistency.

@lhotrifork This has changed the behaviour of the config validation slightly, you could previously omit the secret field, but this will now throw an error.

For example, this is no longer a valid config: (from argo-cd)

staticClients:
- id: argo-cd-cli
  name: Argo CD CLI
  public: true
  redirectURIs:
  - http://localhost

@thesuperzapper an ugly but working workaround is to add secretEnv: THISDOESNOTEXIST, I think.