ingestr 0.13.90__tar.gz → 0.13.91__tar.gz

{ingestr-0.13.90 → ingestr-0.13.91}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ingestr
-Version: 0.13.90
+Version: 0.13.91
 Summary: ingestr is a command-line application that ingests data from various sources and stores them in any database.
 Project-URL: Homepage, https://github.com/bruin-data/ingestr
 Project-URL: Issues, https://github.com/bruin-data/ingestr/issues

{ingestr-0.13.90 → ingestr-0.13.91}/docs/supported-sources/adjust.md

@@ -9,7 +9,7 @@ ingestr supports Adjust as a source.
 The URI format for Adjust is as follows:
 
 ```plaintext
-adjust://?api_key=<api-key-here>
+adjust://?api_key=<api-key-here>&lookback_days=40
 ```
 Parameters:
 - `api_key`: Required. The API key for the Adjust account.
@@ -20,7 +20,10 @@ An API token is required to retrieve reports from the Adjust reporting API. plea
 Once you complete the guide, you should have an API key. Let's say your API key is `nr_123`, here's a sample command that will copy the data from Adjust into a DuckDB database:
 
 ```sh
-ingestr ingest --source-uri 'adjust://?api_key=nr_123' --source-table 'campaigns' --dest-uri duckdb:///adjust.duckdb --dest-table 'adjust.output'
+ingestr ingest --source-uri 'adjust://?api_key=nr_123' \
+--source-table 'campaigns' \
+--dest-uri duckdb:///adjust.duckdb \
+--dest-table 'adjust.output'
 ```
 
 The result of this command will be a table in the `adjust.duckdb` database.
@@ -32,6 +35,13 @@ Adjust data may change going back, which means you'll need to change your start
 ## Tables
 Adjust source allows ingesting data from various sources:
 
+| Table           | PK/Merge Key | Inc Key | Inc Strategy | Details                                                                                                                                        |
+| --------------- | ----------- | --------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Events](https://dev.adjust.com/en/api/rs-api/events)        | id | –  |        replace     | Retrieves data for [events](https://dev.adjust.com/en/api/rs-api/events/) and event slugs.              |                                        |
+| [campaigns](https://dev.adjust.com/en/api/rs-api/reports) | day | –                | merge            | Retrieves data for a campaign, showing the app's revenue and network costs over multiple days. `Columns:` campaign, day, app, store_type, channel, country, network_cost, all_revenue_total_d0, ad_revenue_total_d0, revenue_total_d0, all_revenue_total_d1, ad_revenue_total_d1, revenue_total_d1, all_revenue_total_d3, ad_revenue_total_d3, revenue_total_d3, all_revenue_total_d7, ad_revenue_total_d7, revenue_total_d7, all_revenue_total_d14, ad_revenue_total_d14, revenue_total_d14, all_revenue_total_d21 |
+| [creatives](https://dev.adjust.com/en/api/rs-api/reports)   | day | -     | merge  | Retrieves data for a creative assets, detailing the app's revenue and network costs across multiple days. `Columns:` campaign, day, app, store_type, channel, country, adgroup, creative, network_cost, all_revenue_total_d0, ad_revenue_total_d0, revenue_total_d0, all_revenue_total_d1, ad_revenue_total_d1, revenue_total_d1, all_revenue_total_d3, ad_revenue_total_d3, revenue_total_d3, all_revenue_total_d7, ad_revenue_total_d7, revenue_total_d7, all_revenue_total_d14, ad_revenue_total_d14, revenue_total_d14, all_revenue_total_d21 |
+| `custom`   | `configurable` | -     | merge  | Retrieves custom data based on the dimensions and metrics specified. Please refer to the `custom reports` section below for more information.
+
 #### Custom reports: `custom:<dimensions>:<metrics>[:<filters>]`
 
 The custom table allows you to retrieve data based on specific dimensions and metrics, and apply filters to the data.
@@ -50,13 +60,6 @@ Parameters:
 > [!WARNING]
 > Custom tables require a time-based dimension for efficient operation, such as `hour`, `day`, `week`, `month`, or `year`.
 
-| Table           | PK/Merge Key | Inc Key | Inc Strategy | Details                                                                                                                                        |
-| --------------- | ----------- | --------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Events](https://dev.adjust.com/en/api/rs-api/events)        | id | –  |        replace     | Retrieves data for [events](https://dev.adjust.com/en/api/rs-api/events/) and event slugs.              |                                        |
-| [campaigns](https://dev.adjust.com/en/api/rs-api/reports) | day | –                | merge            | Retrieves data for a campaign, showing the app's revenue and network costs over multiple days. `Columns:` campaign, day, app, store_type, channel, country, network_cost, all_revenue_total_d0, ad_revenue_total_d0, revenue_total_d0, all_revenue_total_d1, ad_revenue_total_d1, revenue_total_d1, all_revenue_total_d3, ad_revenue_total_d3, revenue_total_d3, all_revenue_total_d7, ad_revenue_total_d7, revenue_total_d7, all_revenue_total_d14, ad_revenue_total_d14, revenue_total_d14, all_revenue_total_d21 |
-| [creatives](https://dev.adjust.com/en/api/rs-api/reports)   | day | -     | merge  | Retrieves data for a creative assets, detailing the app's revenue and network costs across multiple days. `Columns:` campaign, day, app, store_type, channel, country, adgroup, creative, network_cost, all_revenue_total_d0, ad_revenue_total_d0, revenue_total_d0, all_revenue_total_d1, ad_revenue_total_d1, revenue_total_d1, all_revenue_total_d3, ad_revenue_total_d3, revenue_total_d3, all_revenue_total_d7, ad_revenue_total_d7, revenue_total_d7, all_revenue_total_d14, ad_revenue_total_d14, revenue_total_d14, all_revenue_total_d21 |
-| `custom`   | `configurable` | -     | merge  | Retrieves custom data based on the dimensions and metrics specified.
-
  ## Examples
 
 Copy campaigns data from Adjust into a DuckDB database:

{ingestr-0.13.90 → ingestr-0.13.91}/docs/supported-sources/airtable.md

@@ -22,15 +22,32 @@ The URI is used to connect to the Airtable API for extracting data. More details
 
 Airtable requires a few steps to set up an integration, please follow the guide dltHub [has built here](https://dlthub.com/docs/dlt-ecosystem/verified-sources/airtable#setup-guide).
 
-Once you complete the guide, you should have an Access Token and a Base ID. The source table you'll use for ingestr will be `<base_id>/<table_name>`.
+Once you complete the guide, you should have an Access Token. 
+
+The source table you'll use for ingestr will be `<base_id>/<table_id>`.
+
+### Getting your Base ID and Table ID
+
+To find your Base ID and Table ID:
+
+1. Log into Airtable and navigate to your base or table
+2. Look at the URL in your browser's address bar when viewing your base
+3. The Base ID always starts with "app" and appears before the next `/`
+4. The Table IDs start with "tbl" and appears before the next `/`.
+
+For example, in this URL:
+```plaintext
+https://airtable.com/appve10kl227BIT4GV/tblOUnZVLFWbemTP1/viw3qtF76bRQC3wKx/rec9khXgeTotgCQ62?blocks=hide 
+```
+In this case base_id is `appve10kl227BIT4GV` and table_id is `tblOUnZVLFWbemTP1`
 
 Let's say your access token is `patr123.abc` and the base ID is `appXYZ`, here's a sample command that will copy the data from Airtable into a DuckDB database:
 
 ```sh
-ingestr ingest 
-    --source-uri 'airtable://?access_token=patr123.abc' 
-    --source-table 'appXYZ/employee' 
-    --dest-uri 'duckdb:///airtable.duckdb' 
+ingestr ingest \
+    --source-uri 'airtable://?access_token=patr123.abc' \
+    --source-table 'appXYZ/employee' \
+    --dest-uri 'duckdb:///airtable.duckdb' \
     --dest-table 'des.employee'
 ```
 

{ingestr-0.13.90 → ingestr-0.13.91}/docs/supported-sources/appsflyer.md

@@ -21,10 +21,10 @@ An API token is required to retrieve reports from the AppsFlyer API, please [fol
 Let's say your API key is `ey123`, here's a sample command that will copy the data from AppsFlyer into a DuckDB database:
 
 ```bash
-ingestr ingest 
-    --source-uri 'appsflyer://?api_key=ey123' 
-    --source-table 'campaigns' 
-    --dest-uri duckdb:///appsflyer.duckdb 
+ingestr ingest \
+    --source-uri 'appsflyer://?api_key=ey123' \
+    --source-table 'campaigns' \
+    --dest-uri duckdb:///appsflyer.duckdb \
     --dest-table 'appsflyer.output'
 ```
 
@@ -40,7 +40,7 @@ ingestr integrates with the [Master Report API](https://dev.appsflyer.com/hc/ref
 | --------------- | ----------- | --------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
 | [campaigns](https://dev.appsflyer.com/hc/reference/master_api_get) | install_time | install_time | merge| Retrieves data for campaigns, detailing the app's costs, loyal users, total installs, and revenue over multiple days.`columns:`  app_id, campaign, geo, install_time, average_ecpi, clicks, cohort_day_1_revenue_per_user, cohort_day_1_total_revenue_per_user, cohort_day_14_revenue_per_user, cohort_day_14_total_revenue_per_user, cohort_day_21_revenue_per_user, cohort_day_21_total_revenue_per_user, cohort_day_3_revenue_per_user, cohort_day_3_total_revenue_per_user, cohort_day_7_revenue_per_user, cohort_day_7_total_revenue_per_user, cost, impressions, installs, loyal_users, retention_day_7, revenue, roi, uninstalls |
 | [creatives](https://dev.appsflyer.com/hc/reference/master_api_get) | install_time | install_time | merge| Retrieves data for a creative asset, including revenue and cost. `columns:` geo, app_id, install_time, campaign, adset_id, adset, ad_id, impressions, clicks, installs, cost, revenue, average_ecpi, loyal_users, uninstalls, roi  |
-| `custom:<dimensions>:<metrics>` | Dynamic (dimensions + install_time) | install_time | merge| Retrieves data for custom tables, which can be specified by the user.|
+| `custom:<dimensions>:<metrics>` | Dynamic (dimensions + install_time) | install_time | merge| Retrieves data for custom tables, which can be specified by the user. Please refer to the `custom Tables` section below for more information. |
 
 Use these as `--source-table` parameter in the `ingestr ingest` command.
 
@@ -48,15 +48,46 @@ Use these as `--source-table` parameter in the `ingestr ingest` command.
 
 You can also ingest custom tables by providing a list of dimensions and metrics.
 
-The table format is as follows:
+The format for the custom table is:
 
 ```plaintext
 custom:<dimension1>,<dimension2>,<metric1>,<metric2>
 ```
-
-This will automatically generate a table with the dimensions and metrics you provided.
+Parameters:
+- `dimensions`: A comma-separated list of [dimensions](https://support.appsflyer.com/hc/en-us/articles/213223166-Master-API-user-acquisition-metrics-via-API#groupings) to retrieve.
+- `metrics`: A comma-separated list of [metrics](https://support.appsflyer.com/hc/en-us/articles/213223166-Master-API-user-acquisition-metrics-via-API#kpis) to retrieve.
 
 For custom tables, ingestr will use the given dimensions as the primary key to deduplicate the data.
 
 > [!NOTE]
 > ingestr will add `install_time` as the primary key to the table by default if it is not provided as one of the dimensions.
+
+
+ ## Examples
+
+Copy campaigns data from Appsflyer into a DuckDB database:
+```sh
+ingestr ingest \
+    --source-uri 'appsflyer://?api_key=ey123' \
+    --source-table 'campaigns' \
+    --dest-uri duckdb:///appsflyer.duckdb \
+    --dest-table 'dest.output'
+```
+
+Copy creatives data from Appsflyer into a DuckDB database:
+```sh
+ingestr ingest \
+    --source-uri 'appsflyer://?api_key=ey123' \
+    --source-table 'creatives' \
+    --dest-uri duckdb:///appsflyer.duckdb \
+    --dest-table 'dest.output'
+```
+
+Copy custom data from Appsflyer into a DuckDB database:
+```sh
+ingestr ingest \
+    --source-uri "appsflyer://?api_key=ey123" \
+    --source-table "custom:app_id,geo,install_time,clicks,install" \
+    --dest-uri duckdb:///appsflyer.db \
+    --dest-table "mat.example"
+```

{ingestr-0.13.90 → ingestr-0.13.91}/docs/supported-sources/appstore.md

@@ -57,70 +57,14 @@ We recommend using `ONGOING` access-type for reports. Please note that it may ta
 
 > [!NOTE]
 > you have to create a Report Request for each individual App that you want to ingest data for. You can use [list apps](https://developer.apple.com/documentation/appstoreconnectapi/get-v1-apps) API to get the list of all apps in your Apple Account.
-### Example: Loading App Downloads Analytics
-
-For this example, we'll assume that:
-* `key_id` is `key_0`
-* `issuer_id` is `issue_0`
-* `key` is stored in the current directory and is named `api.key`
-* `app_id` is `12345`
-
-We will run `ingestr` to save this data to a [duckdb](https://duckdb.org/) database called `analytics.db` under the name `public.app_downloads`.
-
-```sh
-ingestr ingest \
-    --source-uri "appstore://app_id=12345&key_path=api.key&key_id=key_0&issuer_id=issue_0" \
-    --source-table "app-downloads-detailed" \
-    --dest-uri "duckdb:///analytics.db"  \
-    --dest-table "public.app_downloads" \
-```
-
-### Example: Loading Data for multiple Apps
-
-We will extend the prior example with another app with ID `67890`. To achieve this, simply add another `app_id` query parameter to the URI.
-```sh
-ingestr ingest \
-    --source-uri "appstore://app_id=12345&app_id=67890&key_path=api.key&key_id=key_0&issuer_id=issue_0" \
-    --source-table "app-downloads-detailed" \
-    --dest-uri "duckdb:///analytics.db"  \
-    --dest-table "public.app_downloads" \
-```
-
-
-### Example: Incremental Loading
-
-`ingestr` supports incremental loading for all App Store tables.
-
-To begin, we will first load all data till `2025-01-01` by specifying the `--interval-end` flag. We'll assume the same credentials from our [first example](#example-loading-app-downloads-analytics)
-```sh
-ingestr ingest \
-    --source-uri "appstore://app_id=12345&key_path=api.key&key_id=key_0&issuer_id=issue_0" \
-    --source-table "app-downloads-detailed" \
-    --dest-uri "duckdb:///analytics.db"  \
-    --dest-table "public.app_downloads" \
-    --interval-end "2025-01-01"
-```
-
-`ingestr` will load all data available till `2025-01-01`. Now we will run `ingestr` again, but this time, we'll let `ingestr` pickup from where it left off by specifying the `--incremental-strategy` flag.
-
-```sh
-ingestr ingest \
-    --source-uri "appstore://app_id=12345&key_path=api.key&key_id=key_0&issuer_id=issue_0" \
-    --source-table "app-downloads-detailed" \
-    --dest-uri "duckdb:///analytics.db"  \
-    --dest-table "public.app_downloads" \
-    --incremental-strategy "merge"
-```
-
-Notice how we didn't specify a date parameter? `ingestr` will automatically use the metadata from last load and continue loading data from that point on.
 
 ## Tables
 | Table | PK | Inc Key | Inc Strategy | Details |
 |-------|----|---------|--------------|---------|
 | `app-downloads-detailed` | [App Apple Identifier,App Name, App Version,Campaign,Date,Device,Download Type,Page Title,Page Type,Platform Version,Pre-Order,Source Info,Source Type,Territory] | processing_date | merge | App download analytics including first-time downloads, redownloads, updates, and more. |
-| `app-store-discovery-and-engagement-detailed` |  primary_key = [App Apple Identifier,App Name,Campaign,Date,Device,Engagement Type,Event,Page Title,Page Type,Platform Version,Source Info,Source Type,Territory] | processing_date | merge | App Store discovery and engagement metrics including data about user engagement with your app’s icons, product pages, in-app event pages, and other install sheets. |
-|`app-sessions-detailed` |  primary_key=[Date,App Name,App Apple Identifier,App Version,Device,Platform Version,Source Type,Source Info,Campaign,Page Type,Page Title,App Download Date,Territory] | processing_date | merge | App Session provides insights on how often people open your app, and how long they spend in your app. |
-| app-store-installation-and-deletion-detailed | [App Apple Identifier,App Download Date,App Name,App Version,Campaign,Counts,Date,Device,Download Type,Event,Page Title,Page Type,Platform Version,Source Info,Source Type,Territory,Unique Devices] | processing_date | merge | App installation and deletion metrics including device to estimate the number of times people install and delete your App Store apps. |
+| `app-store-discovery-and-engagement-detailed` | [App Apple Identifier,App Name,Campaign,Date,Device,Engagement Type,Event,Page Title,Page Type,Platform Version,Source Info,Source Type,Territory] | processing_date | merge | App Store discovery and engagement metrics including data about user engagement with your app’s icons, product pages, in-app event pages, and other install sheets. |
+|`app-sessions-detailed` | [Date,App Name,App Apple Identifier,App Version,Device,Platform Version,Source Type,Source Info,Campaign,Page Type,Page Title,App Download Date,Territory] | processing_date | merge | App Session provides insights on how often people open your app, and how long they spend in your app. |
+| `app-store-installation-and-deletion-detailed` | [App Apple Identifier,App Download Date,App Name,App Version,Campaign,Counts,Date,Device,Download Type,Event,Page Title,Page Type,Platform Version,Source Info,Source Type,Territory,Unique Devices] | processing_date | merge | App installation and deletion metrics including device to estimate the number of times people install and delete your App Store apps. |
 | `app-store-purchases-detailed`|  [App Apple Identifier,App Download Date,App Name,Campaign,Content Apple Identifier,Content Name,Date,Device,Page Title,Page Type,Payment Method,Platform Version,Pre-Order,Purchase Type,Source Info,Source Type,Territory] | processing_date | merge | App purchase analytics including revenue, payment methods, and content details. |
 | `app-crashes-expanded`| [App Name,App Version,Build,Date,Device,Platform,Release Type,Territory] |processing_date | merge | App crash analytics including crash counts, device information, and version details. |
 
@@ -257,6 +201,63 @@ Use this report to understand crashes for your App Store apps by app version and
 | `unique_devices` | Number of unique devices where app crashed. |
 
 
+## Examples
+### Loading App Downloads Analytics
+
+For this example, we'll assume that:
+* `key_id` is `key_0`
+* `issuer_id` is `issue_0`
+* `key` is stored in the current directory and is named `api.key`
+* `app_id` is `12345`
+
+We will run `ingestr` to save this data to a [duckdb](https://duckdb.org/) database called `analytics.db` under the name `public.app_downloads`.
+
+```sh
+ingestr ingest \
+    --source-uri "appstore://app_id=12345&key_path=api.key&key_id=key_0&issuer_id=issue_0" \
+    --source-table "app-downloads-detailed" \
+    --dest-uri "duckdb:///analytics.db"  \
+    --dest-table "public.app_downloads"
+```
+
+### Loading Data for multiple Apps
+
+We will extend the prior example with another app with ID `67890`. To achieve this, simply add another `app_id` query parameter to the URI.
+```sh
+ingestr ingest \
+    --source-uri "appstore://app_id=12345&app_id=67890&key_path=api.key&key_id=key_0&issuer_id=issue_0" \
+    --source-table "app-downloads-detailed" \
+    --dest-uri "duckdb:///analytics.db"  \
+    --dest-table "public.app_downloads"
+```
+
+### Incremental Loading
+
+`ingestr` supports incremental loading for all App Store tables.
+
+To begin, we will first load all data till `2025-01-01` by specifying the `--interval-end` flag. We'll assume the same credentials from our [first example](#example-loading-app-downloads-analytics)
+```sh
+ingestr ingest \
+    --source-uri "appstore://app_id=12345&key_path=api.key&key_id=key_0&issuer_id=issue_0" \
+    --source-table "app-downloads-detailed" \
+    --dest-uri "duckdb:///analytics.db"  \
+    --dest-table "public.app_downloads"
+    --interval-end "2025-01-01"
+```
+
+`ingestr` will load all data available till `2025-01-01`. Now we will run `ingestr` again, but this time, we'll let `ingestr` pickup from where it left off by specifying the `--incremental-strategy` flag.
+
+```sh
+ingestr ingest \
+    --source-uri "appstore://app_id=12345&key_path=api.key&key_id=key_0&issuer_id=issue_0" \
+    --source-table "app-downloads-detailed" \
+    --dest-uri "duckdb:///analytics.db"  \
+    --dest-table "public.app_downloads" \
+    --incremental-strategy "merge"
+```
+
+Notice how we didn't specify a date parameter? `ingestr` will automatically use the metadata from last load and continue loading data from that point on.
+
 Use these as `--source-table` parameter in the `ingestr ingest` command.
 
 To know more about these reports and their dimensions, see [App Store Analytics docs](https://developer.apple.com/documentation/analytics-reports).

{ingestr-0.13.90 → ingestr-0.13.91}/docs/supported-sources/salesforce.md

@@ -62,9 +62,29 @@ Salesforce source allows ingesting the following objects into separate tables:
 |  `pricebook_entry`   | id | - | replace  | Represents a specific price for a product in a price book. |
 |  `task`   | id | last_timestamp | merge | Used to track and manage various activities and tasks within the Salesforce platform.  |
 |  `event`   | id | last_timestamp | merge | Used to track and manage calendar-based events, such as meetings, appointments, or calls. |
+|  `custom:<custom_object_name>`   | - | - | replace | Track and store data that’s unique to your organization. For more information about custom objects in Salesforce, read [here](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_custom_objects.htm)|
 
 Use these as `--source-table` parameters in the `ingestr ingest` command.
 
+ ## Examples
+ Copy user_role data from Salesforce into a DuckDB database:
+```sh
+ingestr ingest \
+  --source-uri "salesforce://?username=<username>&password=<password>&token=<token>&domain=<domain>" \
+  --source-table "user_role" \
+  --dest-uri "duckdb:///sf.db" \
+  --dest-table "public.user_role"
+```
+
+Copy custom object data from Salesforce into a DuckDB database:
+```sh
+ingestr ingest \
+  --source-uri "salesforce://?username=<username>&password=<password>&token=<token>&domain=<domain>" \
+  --source-table "custom:My__Community_Group__c" \
+  --dest-uri "duckdb:///sf.db" \
+  --dest-table "public.my_community"
+```
+
 > [!WARNING]
 > Salesforce API limits may affect the frequency and volume of data ingestion. Incremental loading is supported for objects with the `SystemModstamp` field, but some objects may require full-refresh loads. This is indicated by `mode` in the tables above. Tables with mode `replace` don't support incremental loads, while the ones with `merge` do.
 

ingestr-0.13.91/ingestr/src/buildinfo.py

@@ -0,0 +1 @@
+version = "v0.13.91"

{ingestr-0.13.90 → ingestr-0.13.91}/ingestr/src/salesforce/__init__.py

@@ -14,6 +14,7 @@ def salesforce_source(
     password: str,
     token: str,
     domain: str,
+    custom_object: str = None,
 ) -> Iterable[DltResource]:
     """
     Retrieves data from Salesforce using the Salesforce API.
@@ -131,6 +132,10 @@ def salesforce_source(
     ) -> Iterable[TDataItem]:
         yield get_records(client, "Event", last_timestamp.last_value, "SystemModstamp")
 
+    @dlt.resource(write_disposition="replace")
+    def custom() -> Iterable[TDataItem]:
+        yield get_records(client, custom_object)
+
     return (
         user,
         user_role,
@@ -147,4 +152,5 @@ def salesforce_source(
         pricebook_entry,
         task,
         event,
+        custom,
     )

{ingestr-0.13.90 → ingestr-0.13.91}/ingestr/src/sources.py

@@ -2525,9 +2525,14 @@ class SalesforceSource:
 
         src = salesforce_source(**creds)  # type: ignore
 
+        if table.startswith("custom:"):
+            custom_object = table.split(":")[1]
+            src = salesforce_source(**creds, custom_object=custom_object)
+            return src.with_resources("custom")
+
         if table not in src.resources:
             raise UnsupportedResourceError(table, "Salesforce")
-
+        
         return src.with_resources(table)
 
 

{ingestr-0.13.90 → ingestr-0.13.91}/pyproject.toml

@@ -94,7 +94,9 @@ exclude = [
     'src/clickup/.*',
     'src/influxdb/.*',
     'src/freshdesk/.*',
-    'src/wise/.*'
+    'src/wise/.*',
+    'src/salesforce/.*'
+
   ]
 
 [[tool.mypy.overrides]]
@@ -128,7 +130,8 @@ module = [
   "ingestr.src.influxdb",
   "ingestr.src.freshdesk",
   "ingestr.src.wise",
-  "ingestr.src.revenuecat"
+  "ingestr.src.revenuecat",
+  "ingestr.src.salesforce",
 ]
 follow_imports = "skip"
 

ingestr-0.13.90/ingestr/src/buildinfo.py

@@ -1 +0,0 @@
-version = "v0.13.90"