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
TASK: Add payment-service SIT configuration to config-repo #162
Preferred merge order: merge #32 first because it establishes the shared Auth/MFA configuration baseline, then merge #33 and #34 in either order. No delay is required. Roll out the affected services after the configuration changes are merged.
The three branches were rebased onto current main, have no merge conflicts, and remain normal non-draft PRs.
The conflicting branch was rebuilt from current main; its scope is now limited to Payment Service defaults/SIT configuration and verification documentation. YAML parsing and diff checks passed. Merge this configuration PR after the Auth/MFA baseline already on main; no fixed delay is required. Roll out Payment Service after its application PR and configuration are merged.
The PR wires the payment_service JDBC URL and PostgreSQL Secret references into the SIT Helm deployment, updates chart metadata to 0.2.0 / 0.0.2, and documents the configuration boundary. Payment and Notification rollout PRs are independent and can merge in either order; no delay is required.
Verification passed locally: Maven verify with Docker-backed Testcontainers, Helm lint/render, and git diff --check.
Startup completed successfully and Flyway connected to PostgreSQL payment_service.
Config Server metadata confirms payment-service/default loads the service defaults/shared defaults and payment-service/sit additionally loads payment-service-sit.yml and application-sit.yml from config-repo/main.
No secrets were printed. The permanent post-merge SIT rollout evidence is complete.
Activity
ramioooz commentedon Sep 4, 2026
Implementation PRs are ready for review:
Preferred merge order: merge #32 first because it establishes the shared Auth/MFA configuration baseline, then merge #33 and #34 in either order. No delay is required. Roll out the affected services after the configuration changes are merged.
The three branches were rebased onto current
main, have no merge conflicts, and remain normal non-draft PRs.ramioooz commentedon Sep 4, 2026
Implementation PR: digital-bank-java/config-repo#34
The conflicting branch was rebuilt from current
main; its scope is now limited to Payment Service defaults/SIT configuration and verification documentation. YAML parsing and diff checks passed. Merge this configuration PR after the Auth/MFA baseline already onmain; no fixed delay is required. Roll out Payment Service after its application PR and configuration are merged.ramioooz commentedon Sep 4, 2026
Implementation is ready for review in payment-service#9.
The PR wires the
payment_serviceJDBC URL and PostgreSQL Secret references into the SIT Helm deployment, updates chart metadata to0.2.0/0.0.2, and documents the configuration boundary. Payment and Notification rollout PRs are independent and can merge in either order; no delay is required.Verification passed locally: Maven
verifywith Docker-backed Testcontainers, Helm lint/render, andgit diff --check.ramioooz commentedon Sep 4, 2026
Local SIT validation completed on 2026-09-05 with the feature-branch artifacts from the linked PR.
0.0.2.The feature artifact was used only for pre-merge runtime validation. The permanent rollout will be repeated after the PR is merged.
ramioooz commentedon Sep 4, 2026
SIT verification evidence (2026-09-05)
Payment Service configuration and deployment are verified from merged mainline changes.
config-repo#34andpayment-service#9are merged.digital-bank-java/payment-service:0.0.2from refreshedpayment-service/main.kubectl rollout restart deployment/payment-service -n digital-bank-sit.sha256:13dfbb184192ec4541b3e0d7cce46323e7689f7d09706f4293c451bf3804502d.0.payment_service.payment-service/defaultloads the service defaults/shared defaults andpayment-service/sitadditionally loadspayment-service-sit.ymlandapplication-sit.ymlfromconfig-repo/main.No secrets were printed. The permanent post-merge SIT rollout evidence is complete.