Consider combining source and destination type to single type

[fleupold]

Given that source and destination fields have exactly the same type it may make sense combining them into one field (e.g. datasources). Otherwise, one will frequently have redundant configurations like:

sources:
  - name: Dune
    type: dune
    key: ${DUNE_API_KEY}
  - name: PG
    type: postgres
    key: ${DB_URL}

destinations:
  - name: Dune
    type: dune
    key: ${DUNE_API_KEY}
  - name: PG
    type: postgres
    key: ${DB_URL}

instead of a more concise

datasources:
  - name: Dune
    type: dune
    key: ${DUNE_API_KEY}
  - name: PG
    type: postgres
    key: ${DB_URL}

[bh2smith]

Totally possible. But sources and destinations have different requirements. Like source requires only read access while destinations require write access. We can do this if you're cool with providing write access to sources.

We could add a field in the type like access type "read or write". Maybee it doesn't matter.

[fleupold]

The way we specify a read only source is the exact same way as a write ressource, isn't it? So I feel like this would be a user config error (currently nothing prevents me from putting a read only sql string in a destination pg config).