Repository navigation
Preserve and correct Compose, Redis, and backend deployment changes - #8
Merged
Merged
Conversation
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.
Preserves the five infrastructure commits left on the local workspace branch, rebased as a single focused change on current
main. Compose gains healthy database/Redis dependencies, local builds for the checked-out Java services, and a deterministic Exchange provider mock. The backend Kubernetes manifest is split into services, local database/Redis resources, HPAs, and disruption budgets, with updated deployment and load-testing documentation.Corrects the inherited issues before review: PostgreSQL is constrained to 17, Redis to 7.4, application defaults use explicit local tags, Order receives the shared JWT configuration, and the provider mock rebases rates for the requested currency and rejects unsupported currencies. The catalog k6 baseline requires HTTP 200 and uses the correct edge/Gateway paths. EKS keeps Redis connection credentials in a Secret, safely patches external service URLs, and installs the reusable Order contract before verification.
Already-merged frontend/product-image changes and submodule pointers are excluded. Frontends remain planned for CDN hosting. Redis endpoint wiring does not implement application caching; Product and Exchange source repositories/images remain external requirements. No services, cluster, load test, or cloud deployment were started for this PR. Please review and merge manually.
Validation:
.pre-commit-config.yaml. Equivalent available checks were run directly.