when I run

tap-slack

the

start_date

config parameter keeps getting reset (in the config json file) to May 1, 2020. Creepily, thats the same exact example date value to set for that. But it’s a bit odd that running elt actually causes it to change from Jan 1, 2020 or any other date to May 1, 2020. Does anyone know a good reason why this may be happening? Do any other taps do this?

@srini_kadamati__apache_superset_ Are you saying it shows up as

2020-01-01

in

meltano config tap-slack

and

meltano config tap-slack list

, but then when you actually run

meltano elt

the value that gets saved in

config.json

is

2020-05-01

?

well to clarify 🙂 I manually over-write the config json file (in sublime text) and save it. Then I run

meltano elt

and it gets reverted to 2020-05-01

Well then this paragraph from https://meltano.com/#meltano-config explains exactly what is happening: 😄

Meltano is responsible for managing the configuration of all of a project's plugins, including its extractors and loaders. It knows what settings are supported by each plugin, and how and when different types of plugins expect to be fed that configuration.

This means that you do not need to manually craft the `config.json` files

expected by Singer taps and targets, because Meltano will generate them on the fly whenever an extractor or loader is used through

meltano elt

or

meltano invoke

.

`Extractor ‘tap-slack’ setting ‘start_date’ was set in `meltano.yml`: ‘2019-01-01T000000Z’ oh interesting, I’m not factoring in

meltano.yml

!

Indeed, you'll want to make sure the new value actually shows up in

meltano config tap-gitlab

, by setting the new value using

meltano config <plugin> set

, or by editing

meltano.yml

directly

right , makes sense