I fallowed https://www.meltano.com/#adding-extractors-and-loaders-to-your-project exact steps to add the custom extractor of covid-19, it has appeared on UI but I can not configure it from UI.

@islomkhon Do the steps described/discussed in https://meltano.slack.com/archives/CFG3C3C66/p1589770089111500 work for you? I hadn't anticipated this amount of interest in the Meltano UI at this point! I'll improve the documentation around known plugins: https://gitlab.com/meltano/meltano/-/issues/2041

I've fixed up the issue.

@islomkhon Great! Let me know if there's anything else I can do to help 🙂

@douwe_maan Now I am trying to add a s3 target to stream data too my aws s3 bucket.

@islomkhon No, as it says on the bottom there, the UI currently only supports the

target-postgres

loader. There's an issue to bring Loader settings back in the UI but it's currently in the Backlog: https://gitlab.com/meltano/meltano/-/issues/1669 The recommended way of configuring and using Meltano right now is through the CLI; is that an option for you?

The UI in this case refers to making the target appear as as the taps would. Not necessaryily using the Analytics. In which case I will need to add the AWS s3 secret & public key before I can connect

@islomkhon The Loaders tap and settings were removed as part of a set of pretty significant UI changes in https://gitlab.com/meltano/meltano/-/merge_requests/1359, so bringing it back will require us to also rethink how it would fit in the current UI, or whether we should revert (some of) those earlier changes. If you have any thoughts on that, could you please weigh in on https://gitlab.com/meltano/meltano/-/issues/1669? If you'd like to work on bringing this back, I'd be more than happy to work with you on that, but it may not be straight forward. It would also help me to understand why you'd prefer to manage these in the UI rather than the CLI and

meltano.yml

at this stage, so that I can manage my own priorities for the project better 🙂

the main reason why I am trying to use UI is that my colleagues are not tech guys. I wanted to make them possible to stream data directly to their s3 buckets

@islomkhon Thanks for the extra context! I've put a couple of thoughts down in https://gitlab.com/meltano/meltano/-/issues/1669#note_345343248 that may help. How familiar are you with Vue.js? 🙂

not too much familiar.

Yep, the component still exists but it's no longer used as of https://gitlab.com/meltano/meltano/-/merge_requests/1359, and can't be inserted into the current UX flow "just like that" because of the many other changes in that MR and ones that followed it. If you don't have much Vue experience, this may be too big of a chunk to try to bite off at once; perhaps there are other improvements you could look at first to get some practice? I could see myself getting to this in a few weeks (or sooner if more people raise this as a priority), but that may not be quick enough for your use case. Am I right in assuming that you would also want multiple configuration profiles per tap/target to be configurable in the UI? That's not currently supported either, but also on my radar for the near future: https://gitlab.com/groups/meltano/-/epics/51

Thank you very much for information.

@islomkhon Yes, that definitely looks like the right first step to making the modal available by URL again (e.g. https://localhost:5000/loaders/target-snowflake). I'd suggest creating a Work In Progress merge request on https://gitlab.com/meltano/meltanoso that I can review your code as you go and give you hints and feedback 🙂

I am not too familiar with gitlab I looked up docs but could not find the place to create Work In Progress merge request

@islomkhon No worries, I'll walk you through it 🙂 You'll want to: 1. fork https://gitlab.com/meltano/meltano using the Fork button on the right 2. add your fork as a remote to your clone of

meltano/meltano

(assuming you've already gone through https://meltano.com/docs/contributor-guide.html#setting-up-your-environment) 3. create a new feature branch with your changes 4. push the feature branch to your fork 5. create a merge request from your feature branch to `meltano/meltano`'s

master

branch through https://gitlab.com/meltano/meltano/-/merge_requests/new 6. Start the MR title with "WIP: " to mark it as Work In Progress, so that it can't be merged until the title prefix is removed 7. Ping me (

@DouweM

) on the MR to have a look! Let me know if that helps!

can you check please if I messed up during the creation of MR

@islomkhon Thanks, I've commented on the MR at https://gitlab.com/meltano/meltano/-/merge_requests/1661#note_346284691. Let's continue the conversation there so we can directly refer to and comment on the changes you've made 🙂