Skip to content

TASK: Make Payment Service deployable in SIT #199

Closed
digital-bank-java/payment-service
#7

Description

@ramioooz

Parent: #98
Sprint parent: #23

Objective

Complete the runtime wiring required to deploy the Payment Service lifecycle implementation safely in local SIT.

Scope

  • Inject the Payment Service PostgreSQL URL, username, and password from the approved SIT Secret contract.
  • Align Payment JWT validation with the platform Auth Service contract, including issuer, signing method, and required internal scope.
  • Assign a new immutable application image tag and matching Helm chart version for the lifecycle implementation.
  • Keep payment provider credentials and production endpoints out of Git.

Acceptance Criteria

  • The Payment Service pod starts with Flyway migrations and reports liveness/readiness UP.
  • PostgreSQL credentials are provided through Kubernetes Secret references, not committed values.
  • Authorized internal requests succeed and invalid or insufficient-scope requests are rejected.
  • Existing idempotency and lifecycle tests remain green.
  • The rollout is documented with exact image/chart versions and related PR links.

Related work

Do not merge or deploy Payment Service PR #6 as the final SIT implementation until these runtime prerequisites are addressed.

Activity

  1. added theissue type on Sep 3, 2026
  2. self-assigned this
    on Sep 3, 2026
  3. ramioooz commented on Sep 4, 2026

    @ramioooz
    MemberAuthor

    Runtime prerequisite implementation is ready for review: payment-service#7.

    This PR adds the SIT JWT trust mode, injects the shared Auth JWT secret through the configured Kubernetes Secret, and bumps the Payment Service image/chart versions to 0.0.2/0.2.0. Maven verification, Helm lint/template validation, and container smoke checks pass.

    Merge order: merge auth-service#6 first; mfa-service#8 may merge in parallel. No delay is required, but deploy only after the Config Repository Payment settings and SIT Secret are available.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions