Hi! Great timing on the sdk release, as I was going to spend my week breaking ground on a new tap anyway! So far, super great. I read the docs, muttered to myself "I guess I just yield rows here?" and it just worked. Quick question, as the docs are still a bit sparse, how would I go about designating a tap config property as a secret, so if I set it via

meltano config tap-yeehaw my_secret hunter2

it goes into the

.env

instead of the

meltano.yml

?

It hasn't been implemented yet, apparently: https://gitlab.com/meltano/singer-sdk/-/issues/77

Ah, dang. Ah well, at least I didn't commit it, haha

@edgar_ramirez_mondragon - That’s correct. We don’t have formal secrets handling as of yet, but you can use the normal “tricks” for handing those off to taps if you are familiar with the singer ecosystem. Also - Singer SDK already supports multiple

--config

inputs, meaning you can send one file for secrets and one for non-secrets. You can also send

--config=ENV

to parse any config options from enviornment variables in the form

<PLUGIN_NAME>_<SETTING_NAME>

.

Yeah, I'll be passing them as env vars when deployed. For local dev I just wanted to use

config set

but I'll just use a

.env

for now, and just go all caps in the readme.