I finally got around to trying out SDA's, and I like them a lot! One difficulty I ran into today was separating out staging and prod configs, particularly for the

io_manager_key

. @jamie was super helpful and pointed me to a way to solve this using

define_asset_job

, but we were chatting about the drawback this causes as I can only materialize assets from jobs now (otherwise, it fails due to the missing config). It would be awesome if I could toggle between configs in some manner in the UI, so I can supply variable configs to the assets I'm materializing without wrapping them in a job. It somewhat feels I'm defeating the point of SDA's by going the route I am. I'll also note that I think the branch deployments are a great solution, but I'm not ready to move my dev work to cloud yet.

What if you use the same io_manager_key in the assests, but swap the actual io-manager behind that key in your definitions based on your environment?

Yeah, we do the above, where we configure the resources differently based on stage/prod, but pass the same objects /keys in