iterable_etl DEPRECATED
Replicate data from iterable in databricks
Usage
CLI
python -m iterable_etl --table <table-name>
where is one of the following: campaign_history, campaign_metrics, campaign_list_history, list, or ALL.
API
from iterable_etl.tables.campaign_history import campaign_history_df
from iterable_etl.tables.campaign_metrics import campaign_metrics_df
from iterable_etl.tables.list import list_df
from iterable_etl.tables.campaign_list_history import campaign_list_history_df
campaign_history_df()
campaign_metrics_df()
list_df()
campaign_list_history_df()
Further configs are set via environment variables:
ITERABLE_KEY: API accessAPP_ENV: <development/production> - debug modeSAMPLE_OUTPUT: <True/False> - Save dataframes to csv
DEV
Create venv
python -m venv env
Activate venv
- unix
source env/bin/activate
- windows
env\Scripts\activate.bat
Install Packages
pip install -r requirements.txt
Test
make test
Format
make format
make lint
Version & Release
bump2version <major/minor/patch>
make release
note Don't forget to git push with --tags
pre-commit
Setup
pre-commit install
Run all
make pre-commit
Metadata
Release files for iterable-etl 0.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iterable_etl-0.2.3.tar.gz | 8.3 kB | Without provenance | Details for iterable_etl-0.2.3.tar.gz |
Release files / iterable_etl-0.2.3.tar.gz
| Download URL | iterable_etl-0.2.3.tar.gz |
|---|---|
| Size | 8.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
25268591ab04b28b96c5a518dd148232c51fd877c156a2be7efd735228af2c37
|
|
BLAKE2b-256 checksum How to use checksums |
3d56b68bce58fcd704389d133826a1550b34367011bdd244d7e8a253f296b10a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for iterable-etl 0.2.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.