> Ideally we need to remove most of our env vars from /run to /init, I agree. > But wouldn't it be a breaking change then? >
I don't think so - the first time a container is started, the values are provided on init. On run, the values that change would be provided (activation id, deadline). > Coming back to my original question, I'm ok with leaving the env vars on > the root level of the json object. I think Carlos already has PRs that > could enable that functionality. > Yes I think this is fine - would permit more vars to be passed on as env vars as well in the future. -r
