Can you set env variables in `workspace.yaml`? I t...
# announcements
d
Can you set env variables in
workspace.yaml
? I tried similar syntax to the
dagster.yaml
and that didn’t seem to work
d
Yeah, not currently possible. I'd be interested to hear your use case - my intuition is that the workspace configuration is usually more static / wouldn't typically require secrets or many of the other common use cases for env vars in dagster.yaml
d
Just with our ECS setup it would be helpful to pass in the host name for a grpc as an env
d
That would be a quick change to make it possible to use an env var - but do you expect it to change much once it's first set? Due to some quirks of the system, when the workspace entry changes, it also invalidates any running schedules or sensors.
d
That’s good to know. I don’t think it would change very often, just when we add additional workspaces
d
oh, and to clarify, adding a new one wouldn't affect anything with existing entries - just if you change the hostname for an existing workspace entry
👍 1
c
Another case where a workspace.yaml can be non-static is if you’re using a different pipenv per repo, resulting in non static executable paths per user during local dev
d
Just following up here - next week's release will have the ability to use env vars for the gRPC host and port in the workspace
d
Awesome. Looking forward to it