I’m curious how others who are using the Dagster-Airbyte-Config-As-Code are handling their stream configurations? Right now, for the sake of simplicity, I’m just creating it as a dict and passing it into the

AirbyteConnection

, but I would prefer to keep the configuration separate from the application build. I would think a YAML configuration would make sense, especially as our number of streams grows, but wondering the best approach to exclude it from the application, yet still reference it when defining those connections.