πŸ¦† Effortless Data Quality w/duckdb on GitHub ♾️

adriens - Jul 25 '23 - - Dev Community

πŸͺ Teaser (for the impatients)

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.

🍿 Demo

Enough talks, let's jump'in:

πŸ¦†πŸ’»πŸ”πŸ”§β™ΎοΈπŸ¦† opt-nc/setup-duckdb-action

GitHub logo opt-nc / setup-duckdb-action

πŸ¦† Blazing Fast and highly customizable Github Action to setup a DuckDb runtime

semantic-release πŸ›‘οΈ CodeQL πŸš€ Release

ℹ️ Setup Duckdb Action

This action installs duckdb with the version provided in input.

πŸ“œ Inputs

version

Not Required The version you want to install. If no version defined, the latest version will be installed.

πŸš€ Example usage

uses: opt-nc/setup-duckdb-action@v1.0.8
with:
  version: v1.0.0
Enter fullscreen mode Exit fullscreen mode
uses: opt-nc/setup-duckdb-action@v1.0.8
Enter fullscreen mode Exit fullscreen mode

πŸ“‘ Related resources




πŸ”­ Further πŸŽ€

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:

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .