adam_roderick
05/14/2020, 1:50 PMdouwe_maan
05/14/2020, 6:15 PMconfig objects on your plugins' definitions in meltano.yml for non-sensitive values, which I intend to make more accessible through meltano config soon: https://gitlab.com/meltano/meltano/-/issues/2013.
For sensitive values, environment variables are your best bet since many systems exist to manage them in production environments, some of which also support hiding the most sensitive ones in vaults.
I would love it if Meltano would develop into a more scalable, more mature direction on this front.
The 2 paragraphs I just wrote above could be the start of a "Production" section in the docs, and I think we should discuss more forward-thinking solutions in an issue.
Since you appear to have some thoughts on the topic, I would suggest creating an issue to get the conversation started, and I will update the docs with what I wrote above: https://gitlab.com/meltano/meltano/-/issues/2038edgar_ramirez_mondragon
05/14/2020, 10:08 PM<https://github.com/segmentio/chamber> in a production setting).
An example of a local environment using docker compose (meltano + meltano db + some source + some target)
would be incredibly helpful.edgar_ramirez_mondragon
05/14/2020, 10:08 PMconfig.json is such a hallmark of Singer taps and targets,
the configuration could be stored in a temp file so in the background a tap -c config.json runs and taps remain compatible with the rest of the ecosystemdouwe_maan
05/14/2020, 10:26 PMAn example of a local environment using docker compose (meltano + meltano db + some source + some target)
would be incredibly helpful.I agree this would be useful, and I created a related issue at https://gitlab.com/meltano/meltano/-/issues/1970, although my thinking there was that this would be primarily useful for people wanting to use Meltano UI. In any case, what you describe should already be possible in principle—perhaps you would like to have a crack at setting it up and I can help out if you run into any issues?
douwe_maan
05/14/2020, 10:28 PMAlso, sinceis such a hallmark of Singer taps and targets,config.json
the configuration could be stored in a temp file so in the background aThis is already what happens, right? Whenruns and taps remain compatible with the rest of the ecosystemtap -c config.json
tap-gitlab is run through meltano elt or meltano invoke, Meltano automatically generates .meltano/run/tap-gitlab/tap.config.json which is then passed to the tap executable in the --config flag. Or am I misunderstanding what you're suggesting? 🙂douwe_maan
05/15/2020, 4:35 PM