Does anyone know working with the new environments feature if you need to configure extractors in every every environment you want to use or is it possible to just do certain ones? https://meltano.com/docs/environments.html#inheritance

@edgar_ramirez_mondragon can you answer this?

Sure simple smile. @drew_ipson you can configure as many plugins as you like in any given environment. If a plugin hasn't environment-specific config, Meltano will fall back to other setting sources (top level

plugins

in

meltano.yml

, the system db,

.env

, etc.

@edgar_ramirez_mondragon @taylor Thank you for your help and references! That makes sense. Will they all reference .env file if I don’t configure the environment env?

@drew_ipson If you don't declare config values elsewhere, then yes, it will read from

.env

@edgar_ramirez_mondragon Awesome thanks! Another question I have is my loaders are not being recognized by environment. Do you know why my loaders would not install that are specific to my environments?

@drew_ipson Can you share the contents of

meltano.yml

? You still have to define plugins globally so they're installed by Meltano:

environments:
- name: prod
  config:
    plugins:
      loaders:
      - name: target-postgres
        config:
          dbname: prod
plugins:
  loaders:
  - name: target-postgres
    pip_url: pipelinewise-target-postgres
    variant: transferwise

@edgar_ramirez_mondragon Thank you for your help that is exactly what I was looking for! My meltano.yml now reflects the example you shared. Thanks again!

@drew_ipson that's great 😄! I forgot to mention also our own Meltano² project which may serve as reference as we'll adopt edge features at the earliest

@edgar_ramirez_mondragon that’s awesome! dancingpanda I see that multi-meltano.yaml files are being used in this project also. This will serve as a great guide for how I can implement that. I’m excited to adopt theses awesome features but still learning Meltano!