I have a situation where a standard supported Melt...
# best-practices
m
I have a situation where a standard supported Meltano tap requires a single line change in the source code, and so I've added it as a custom tap (forking the git repo, changing the line, installing from the forked repo) Is there a better way of handling this situation?
The tap in question - https://github.com/singer-io/tap-pendo/issues/80 I've asked if the change can be added to config for the tap, which would simplify things, but until then I guess I'm left with a fork of the tap
a
That's probably the best way for now. I took a look at that repo and there are a TON of PRs that haven't been merged so it might be worth making a fork and putting it in MeltanoLabs.
m
Thanks @amanda.folson! Never considered that if I add it as a variant in Meltano labs then I'll be able to add as a specified variant in Meltano
@amanda.folson maybe there is an intermediary step before adding it to Meltano Labs (I guess Meltano labs is pro That intermediary step would be adding my own fork as a variant on the hub? https://hub.meltano.com/extractors/pendo
In any case, I'm going to try fix that issue, and so if I manage, please let me know where best to share my fixes 😄
t
@matt_arderne yes, we can definitely add your variant as an option on the Hub! If you’d like to transfer it to MeltanoLabs too we can do that, but we’d ask for some base level of committment for PR and issue review 🙂
m
Ok great thanks @taylor. I'll speak with my client as I'll lose access so probably not best placed for ongoing, but would like to encourage them to look into it
t
Sounds good! Let me know if you’d like someone from the Meltano team to chat with them as well 👍