I might be using this wrong but I was just trying to run

meltano invoke --dump=config <plugin>

since I was having connection issues and it looks like its trying to connect (maybe running discover) prior to dumping my config file. Whats being executed behind the scenes when I run this command? I would expect it to just spit out my config for me for validation. I ended up having to go into the

.meltano

directory and catch the temp config file before it was deleted (turns out I was missing a field in my settings)

I remember Douwe responding to someone else about this. Vaugely it was something like Meltano decides to run discovery first before dumping the config. It should be configurable. This is just memory have to dig for his comment

thanks Derek - that gives me some clarity into whats happening at least. This might be an extension of that issue (if one exists)

Glad I could help! Hopefully it helps

jackpot! nice find. I'm going to post my comments there