Closed ryanlovett closed 11 months ago
Writing from my mobile, its a breaking change introduced in kubespawner 5.0.0 i think. Im writing from a mobile, but it should be announced in the changelog.
@consideRatio I see it now, https://github.com/jupyterhub/kubespawner/pull/642, thanks! Testing...
@consideRatio Double braces worked perfectly. I'm going to note in our local docs to check upstream changelogs when we bump major/minor versions!
Sorry for the noise, and thanks again!
Bug description
We had been setting the value of a
singleuser.extraEnv
variable to a json string. When we updated to 3.0.1 helm chart, kubespawner started to fail in_expand_user_properties
when invokingtemplate.format
and user servers would not spawn.Expected behaviour
extraEnv values would not affect spawning.
Actual behaviour
User servers would not spawn.
How to reproduce
Set an singleuser.ExtraEnv var, e.g.
For user
user1
, the hub raises:In investing this, I added some debugging to kubespawner, and logged the template value:
Initially the variable value was more complex, but I reduced it to this simpler reproducible string for debugging. We had been setting something like:
Simple values like
DEBUG_EXTRA_ENV: FOO
work fine.Your personal set up
We just updated to 3.0.1 helm chart from 2.0.1-0.dev.git.6085.h59225bad. Our deployment is at https://github.com/berkeley-dsep-infra/datahub. In this case the extraEnv setting is in a sops-encrypted file.