Skip to content

BUG: add Transaction Service SIT PostgreSQL configuration #190

Closed
1 of 1 issue completed
Closed

Description

@ramioooz

Parent: EPIC: Sprint 3 - Internal Transfers and Event Consistency #21
Related story: STORY: Orchestrate transfer saga with ledger-driven completion #103
Related PRs: config-repo#30, transaction-service#13

Observed

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.

Activity

  1. added theissue type on Sep 3, 2026
  2. ramioooz commented on Sep 3, 2026

    @ramioooz
    MemberAuthor

    Rollout verification on 2026-09-03:

    • 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.

    Fix PRs:

    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.

  3. ramioooz commented on Sep 3, 2026

    @ramioooz
    MemberAuthor

    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.

  4. self-assigned this
    on Sep 3, 2026
  5. ramioooz commented on Sep 3, 2026

    @ramioooz
    MemberAuthor

    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.

  6. ramioooz commented on Sep 3, 2026

    @ramioooz
    MemberAuthor

    Resolved by merged transaction-service#14 and config-repo#37, then verified in SIT after the Transaction Service rollout:

    • Transaction Service is deployed with the transaction_service PostgreSQL datasource.
    • Pod is 1/1 Running with zero new restarts.
    • Application startup completed successfully and the liveness/readiness health groups report UP.

    Closing this database-configuration bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions