So I managed to make this work by using env in the cluster.yaml for both worker and head node types. the only problem is is that value of the variable needs to be hardcoded in the yaml. Although this is fine for regular environment variables for sensitive values it would be nice if there was a way to pass those values by variable name. Is there anything like that supported currently?
I have the same question as @doru1004; the provided link seems 404.
I don’t want to have to put any sensitive environment variables in the config file. I’d prefer to commit the config file and inject the environment variables when running ray up config.yaml. Something like how docker does it would slick. docker run -e myhost='localhost'