Add workflow for custom taps and targets
Problem to solve
Summarize the problem we are trying to solve in the form of we need to do [A], so that [B] can [C]
We currently don't support many taps and targets and this poses risk to adoption. We would like to have a very clear explanation / workflow for anyone willing to contribute
(For whom are we doing this? Include a persona)
(Include use cases, benefits, and/or goals)
By adding more taps and targets, we hope to be able to increase adoption by allowing companies to bring many different data sources in 1. Developing taps and targets in Singer is painful and we believe that by making this process smoother, we can improve the Singer contributing community, which is currently a roadblock to adoption for us.
(How are we going to solve the problem? Try to include the user journey)
Add custom switch to
meltano add- we should be able to add any tap/target bypassing discovery.yml from the CLOI
- Document steps required to create a custom tap and target
What does success look like, and how can we measure that?
(Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this)
Links / references
Please note that this was taken from GitLab, to be changed accordingly
/label ~"To Do"