For some reason a lot of integer fields are being output as `<value>.0` which breaks normalization. This is also happening in other sources, Shopify and Recurly. We need to root cause this issue or roll out a wider fix, perhaps using the CDK. For now, we're just trying to unblock the user.
Release CDK 0.1.1. Unfortunately I can't release 0.1.0 because we previously released it while testing and I didn't realise once a package is released on PyPi, a package with the same name/version cannot be released regardless of whether it's deleted or not.
Updated:
- source-exchange-rates
- source-github-singer
- source-slack
- source-smartsheets (this is at 0.1.4 since someone published 0.1.3 but the change was not checked in)
- source-stripe
Only source-github-singer and source-smartsheets need to be updated. The rest are either not already published or have singer equivalents present.
* Only add the account ID header if set on the Stream
This allows the stream to be used with the "default" account ID,
without worrying about Connect.
Additionally, set a reasonable `primary_key` for Stripe streams,
which seems to be required.
* Update schema to match records returned by read
* Refunds & Bank Accounts streams for stripe (#3030)
Add two new streams:
Refunds - incremental stream.
Bank Accounts - full refresh stream.
* Refunds & Bank Accounts streams for stripe (#3030)
Update quotes in source.py file.
* Refunds & Bank Accounts streams for stripe (#3030)
Add state for `refunds` stream to sample_files/state.json file.
Update catalog data for `refunds` and `bank_accounts` streams in sample_files/full_catalog.json file.
* Refunds & Bank Accounts streams for stripe (#3030)
Update source-stripe connector version from `0.1.0` to `0.1.1`.
Template generation for new Source using the Santa CDK - provide basic scaffolding for someone implementing a new source.
General approach is to buff up comments in the original SDK, and add TODOs with secondary comments in the generated stub methods, as well as links to existing examples (e.g. Stripe or ExchangeRate api) users can look at.
Checked in and added tests for the generated modules.
