You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
BUG: add Transaction Service SIT PostgreSQL configuration #190
The merged Transaction Service SIT configuration contains Kafka settings but no PostgreSQL datasource configuration. Deploying the merged Transaction Service image causes startup failure because Flyway cannot create a datasource.
Expected
Transaction Service should receive the SIT PostgreSQL URL and credentials using the same shared Secret convention as Account and Ledger Service.
Acceptance criteria
Add spring.datasource.url for the transaction_service database.
Inject DB_USERNAME and DB_PASSWORD from the shared SIT Postgres Secret.
Keep credentials out of Git.
Verify Config Server returns the datasource properties for transaction-service/sit.
Deploy the merged Transaction Service image and confirm startup, Flyway migration, health probes, and Kafka configuration.
Cross-link the implementation PR and close this bug after SIT verification.
This is a blocking configuration defect discovered during the first rollout attempt.
Ledger Service image 0.0.3 built from merged ledger-service#17 commit f17a037 and deployed successfully.
Account Service image 0.0.3 built from merged account-service#38 commit 2a42e67 and deployed successfully.
Transaction Service install failed because transaction-service/transaction-service-sit.yml had Kafka settings but no PostgreSQL datasource, and its Helm chart did not inject the shared Postgres Secret.
The failed Transaction release was removed from SIT; no broken workload was left running.
Merge config-repo#37 first, then transaction-service#14. No fixed delay is required. This bug remains open until both are merged and Transaction Service is healthy in SIT.
The datasource and Secret fixes were merged and verified. Transaction now reaches security initialization but fails because its OAuth2 resource-server expects issuer/JWK configuration, while the current Auth Service foundation issues HMAC JWTs and does not expose JWKS. This is tracked as child Bug #191. Authentication will remain fail-closed; no insecure startup workaround will be applied.
The implementation changes from transaction-service#14 and config-repo#37 are merged. Transaction Service mainline verification passes ./mvnw verify with 80 unit-phase tests and 15 PostgreSQL-backed integration tests.
The defect cannot be closed yet because the service has not been deployed and verified in digital-bank-sit. The next rollout also requires transaction-service#15 and config-repo#38.
Activity
ramioooz commentedon Sep 3, 2026
Rollout verification on 2026-09-03:
0.0.3built from mergedledger-service#17commitf17a037and deployed successfully.0.0.3built from mergedaccount-service#38commit2a42e67and deployed successfully.transaction-service/transaction-service-sit.ymlhad Kafka settings but no PostgreSQL datasource, and its Helm chart did not inject the shared Postgres Secret.Fix PRs:
transaction_servicedatasource configuration.DB_USERNAMEandDB_PASSWORD, bump Helm chart to0.2.1.Merge config-repo#37 first, then transaction-service#14. No fixed delay is required. This bug remains open until both are merged and Transaction Service is healthy in SIT.
ramioooz commentedon Sep 3, 2026
The datasource and Secret fixes were merged and verified. Transaction now reaches security initialization but fails because its OAuth2 resource-server expects issuer/JWK configuration, while the current Auth Service foundation issues HMAC JWTs and does not expose JWKS. This is tracked as child Bug #191. Authentication will remain fail-closed; no insecure startup workaround will be applied.
ramioooz commentedon Sep 3, 2026
2026-09-04 verification update
The implementation changes from transaction-service#14 and config-repo#37 are merged. Transaction Service mainline verification passes ./mvnw verify with 80 unit-phase tests and 15 PostgreSQL-backed integration tests.
The defect cannot be closed yet because the service has not been deployed and verified in digital-bank-sit. The next rollout also requires transaction-service#15 and config-repo#38.
ramioooz commentedon Sep 3, 2026
Resolved by merged
transaction-service#14andconfig-repo#37, then verified in SIT after the Transaction Service rollout:transaction_servicePostgreSQL datasource.1/1 Runningwith zero new restarts.UP.Closing this database-configuration bug.