Repository navigation
feat: harden payment idempotency and internal authorization - #4
Merged
ramioooz merged 1 commit intoSep 1, 2026
Conversation
This was referenced Aug 31, 2026
This was referenced Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
payment.internalscope, including documented Problem Details responses.Tracking
Dependencies and merge order
feature/163-payment-http-api.feature/163-payment-http-apifirst, then merge payment-service#3 into itsfeature/161-payment-lifecyclebase.main.Verification
./mvnw --batch-mode --no-transfer-progress spotless:apply: PASS.git diff --check: PASS../mvnw --batch-mode --no-transfer-progress verify: PASS; 15 unit tests and 12 PostgreSQL-backed integration tests ran with 0 failures, 0 errors, and 0 skipped.helm lint helm --strict --values helm/values-sit.yaml: PASS; 1 chart linted, 0 failed.SIT/cluster verification was not run locally because no SIT cluster or deployment credentials are available. The CI smoke configuration now provisions disposable PostgreSQL and supplies non-secret test configuration through the mock Config Server.