This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/pip/dbt-postgres-gte-1.10.1-and-lt-2.0
in repository
https://gitbox.apache.org/repos/asf/fineract-business-intelligence.git
discard 833ebdd build(deps): update dbt-postgres requirement
add a129045 doc: add README and some script changes
add 1507541 Merge pull request #22 from airajena/docs/add-readme
add 877edea build(deps): bump actions/cache from 5.0.5 to 6.1.0
add f05d935 Merge pull request #26 from
apache/dependabot/github_actions/actions/cache-6.1.0
add fe33d1d build(deps): update dbt-postgres requirement
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (833ebdd)
\
N -- N -- N
refs/heads/dependabot/pip/dbt-postgres-gte-1.10.1-and-lt-2.0 (fe33d1d)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.env.example | 36 +-
.github/workflows/apache-rat.yml | 2 +-
README.md | 555 ++++++++++++++++++++-
compose.yaml | 31 +-
dbt/models/marts/facts/fact_delinquency_event.sql | 7 +
dbt/requirements.txt | 2 +-
docker/extractor/Dockerfile | 12 +
.../initdb/002_create_warehouse_roles.sh | 2 +-
scripts/bootstrap_source.sh | 195 ++++++++
scripts/run_pipeline.sh | 84 ++++
warehouse/seed/seed_fineract_source.sql | 389 +++++++++++++++
11 files changed, 1292 insertions(+), 23 deletions(-)
create mode 100644 scripts/bootstrap_source.sh
create mode 100644 scripts/run_pipeline.sh
create mode 100644 warehouse/seed/seed_fineract_source.sql
