#7848 bug: environment configs dont work with mappers
Issue created by pnadolny13
It seems like mapper configs can only be set at the top level. This is either a bug or should be documented clearly in the inline data mapping guide https://docs.meltano.com/guide/mappers.
Here are a few screenshots to illustrate the current behavior. It pulls a public file, adds a mapping for ipv4prefix then loads it to target-csv. The first column of the CSV is what we're expecting the change.
Scenario 1: Raw input, no ipv4prefix, no environment configScreen Shot 2023-06-26 at 3 33 44 PM
Outcome - the raw data for ipv4prefix is output in the first column of the CSV.
Scenario 2: Hardcoded top level mapper for ipv4prefix, no environment configScreen Shot 2023-06-26 at 3 33 17 PM
Outcome - the hardcoded mapping value is output for ipv4prefix in each record.
Scenario 3: Hardcoded top level mapper for ipv4prefix moved into the environment config and commented out at the top levelScreen Shot 2023-06-26 at 3 34 21 PM
Outcome - the raw data for ipv4prefix is output as if there were no mapper.
meltano/meltano