Working on an SDK version of tap-chargebee with the Hotglue version as a baseline, if of any interest

Great @gary_james I worked a lot with this version of the tap and I think that a new version is needed as this version is a little messy. Thanks! The Chargebee API has some strange bugs that had to be handled there, like some endpoints that cannot have date filtering in the first run, if you ever find something strange send me a message and I can take a look if I ever faced this issue before.

awesome, thanks! yeah I've definitely over-simplified things in this current SDK version of the tap, just to get going, but have noticed the other tap isn't so simple so assumed I'd be missing a lot of API specific info 😅

they can be fixed when a user get the error, because most of them are rare and specific, many users were using in production the tap when some of the bugs were find, using the sdk will help a lot in the maintenance 😄

Let us know how it goes!

to be honest I've had basically zero issues, which worries me immensely now 😹 gonna do a bit of validation on the data for this version vs hotglue, but the account I'm testing on is quite new so maybe that's why I'm not uncovering issues (also haven't gone as granular with schema typing for nested objects) or it's just the SDK absolutely crushing it

You may be doing this already, but if you want to be extra sure that the schema matches your records (and other checks) you can check out https://sdk.meltano.com/en/v0.30.0/testing.html#testing-taps