hey folks! i'm using Meltano's environments to vary

start_date

config values for an extractor but it seems to not be seeing the start date param at all and throws

Exception: Config is missing required keys: ['start_date']

. i'm threading the contents of the relevant parts of my

meltano.yml

and an additional

environments.meltano.yml

Looks like the CLI mode of setting the setting name and kind at the same time may not be working as expected:

- name: start_date|date_iso8601
    - name: user_agent|string
    - name: consumer_key|password
    - name: consumer_secret|password
    - name: access_token|password

right off the bat Meltano logs

Environment 'dev' is active

so it's definitely seeing the environment definition

I think the setting declarations should probably be something like:

- name: start_date
      kind: date_iso8601

ahh okay i'll try that

Awesome! 😄

how would i know if it was a bug or issue with how it was invoked?

Do you remember if you added via

meltano add extractor

with the

--custom

flag or in another method? If you go through the

--custom

wizard and ended up with

name|kind

on the same line (as above), that seems like a bug to me and we should probably look into whether we can repro it.

i don't remember but fwiw the extractor was configured several months ago and was running without errors before trying to vary config by environment

Okay, thanks for that info. When environments are used, we somewhat intentionally are more careful about what env vars we inject. And in this case, the concatenated longer names probably prevented an exact name match necessary for injection.

got it, okay

Cc @edgar_ramirez_mondragon in case I'm missing something. But I do think it would make sense that the exact name match requirement was being blocked by the longer concatenation of name and kind. Should be resolved by putting both on separate lines as in this case. And then yes, going forward, any time you see the pipe delimited show up in yaml in the future, let's see if we can see what generated that.

okay i've refactored any instances of that piped syntax so i'll let you know if this comes up again

Thanks, @prratek_ramchandani! 👍

Catching up... Perhaps the

:

delimiter was confused with

|

?

Ahhhhh - perhaps so! 💭