Do you have a repository that relies on
csv files... and want to operate:
- 🛡️ Protect your data with quality intergrity checks before to corrupt your data
- 🔬 Check data quality as part of your project lifecycle
- 📊 Get operational KPIs reporting
- ♾️ Automate release process to explain your contributors what has been achieved
- 📦 Deliver data
- 🤯 Endless usages
Don't look further, this sort post will cover all these aspects with a practical and highly understandable workflow.
Enough talks, let's jump'in:
🦆 Blazing Fast and highly customizable Github Action to setup a DuckDb runtime
ℹ️ Setup Duckdb Action
This action installs
duckdb with the version provided in input.
Not Required The version you want to install. If no version defined, the latest version will be installed.
🚀 Example usage
uses: firstname.lastname@example.org with: version: v0.8.1
Once CI (Continuous Integration) has been done... you can also think (without a lot of efforts) to Deliver that data to third party services, as part of your DEVOPS pipeline.
A this point I see two easy options:
... which make your data available for new usecases, at no additional effort: