planning any support to inject env vars into yaml?

this is a great alley-oop for @alex to dunk

ya im working on adding new config types as we speak - they would support

key: "the value"

or

key:
  env: ENV_VAR_FOR_VALUE

boom

https://dagster.phacility.com/D1956 hoping to get it out in our next release projected for Tue of next week

boooooom

ETA to master will be pending the message thread alex and I had going about the right direction to go with that diff

nw. great to know its coming at least

an obvious plant

any plans in the pipes for mapping resources to different names? the db_info resource in the examples is really great but after creating a generic sql_solid I was hoping the purpose could be to reuse that solid for multiple databases. but currently you would have to define a new resource for every one you would want to connect to in the pipeline yaml. seems a little silly or maybe I'm just doing it wrong.

yep - definitely something we know we need. In fact we built it once already and just recently removed it upon realizing it was totally broken.