Skip to content

fix: bind production batch ports to loopback - #129

Merged
dev-ant merged 2 commits into
mainfrom
fix/origin-port-binding
Nov 3, 2026
Merged

dev-ant merged 2 commits into
mainfrom
fix/origin-port-binding

Conversation

@dev-ant

@dev-ant dev-ant commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Summary

  • bind the Batch application and Elasticsearch 9200/9300 host ports to 127.0.0.1
  • retain Docker network, container ports, image, and volume contracts
  • document the required one-time Elasticsearch-only recreation because normal deploy replaces spring-app only
  • add workflow contract coverage for rollout and rollback safeguards

Validation

  • Java 21 standard verify: passed
  • workflow contract: 6/6 passed
  • secret scan and synthetic Compose render: passed
  • independent re-review: prior Elasticsearch rollout finding resolved

Scope

Specification v1 SHA-256: 09AB4087C7F97082AD2D6FED49EDDF1398D15984CEAA91EC02944D4C641ED805

The Elasticsearch recreation must use the current Compose project, exact running image ID, and existing volume after the ordinary Batch deployment. DNS is unchanged.

@dev-ant
dev-ant merged commit 82f3b15 into main Nov 3, 2026
8 checks passed
@dev-ant
dev-ant deleted the fix/origin-port-binding branch November 3, 2026 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant