bb-fuel
bb-fuel copied to clipboard
Backbase
Backbase DBS data loader tool for test and demo data.
## Description This PR adds a new profile to ingest data into the ephemeral runtimes. ``` THIS IS STILL AN EXPERIMENT ```
This PR is to create new users `fi_credscr_only`, `fi_budgets_only`, `without_credscr_and_budgets` and `credscr_and_budgets` to have respective entitlements only on FI dashboard. For example FI dashboard contains credscr, budgets, etc. for fi_credscr_only...
When using a client repo proxy (which is normal on customer projects not sharing the master credentials) the wagon urls will not work: https://repo.backbase.com/specs/accessgroup-integration-service accessgroup-integration-inbound-api-v2.2.0.yaml the /specs path is not...
#### Version: 12.1 #### Problem The transaction is response is '[]' for all accounts. There is some warnings when I run the edge service and ingest local DBS, not sure...
In case you are ingesting data to an environment where Transaction Signing is enabled, the creation of the payments via the POST API call will fail returning a 401 error...
### The problem When the user tries to ingest data using the local profile the execution fails. It's happening in the `2.6.45` version. ### Command ``` java -Dspring.profiles.active=local -Denvironment.domain=backbase.eu \...
During the bb-fuel data ingestion the full name of the user `full_name_up` is added twice in the field Example of data in the `en_user` table ``` +--------------+-----------------------------+ |external_id |full_name_up |...
The `/actuator/health` endpoint is used when `-Dhealthcheck.timeout.in.minutes=10 -Dhealthcheck.use.actuator=true` It's calling the wrong endpoint. The called URL has either `/client-api` or `/integration-api` in it's path. It should be e.g. /api/access-control/actuator/health and...
At the moment all the endpoints listed in the various `application-*.yml` files are based on plain `http`. There is a growing need to run `bb-fuel` against the same secured endpoints...