Skip to content

STORY: Consolidate runtime environments around SIT, UAT, and PROD #115

Closed
3 of 3 issues completed
Closed

Description

@ramioooz

Parent: EPIC: SIT Deployment and Developer Workflow

Objective

Replace the LOCAL-DEV runtime environment with a three-environment model: SIT, UAT, and PROD.

Scope

  • Make local Docker Desktop Kubernetes the SIT environment for integrated development and testing.
  • Remove active local Spring-profile configuration from the served configuration repository.
  • Document IDE workstation debugging against SIT using temporary Kubernetes port-forwards and overrides.
  • Align Config Server and Insomnia documentation with Base Environment, SIT, UAT, and PROD.
  • Keep CI fixture default configuration as a test mechanism, not a deployment environment.
  • Do not introduce Docker Compose as a parallel local infrastructure stack.

Acceptance Criteria

  • No supported runtime configuration or active documentation presents LOCAL-DEV/local as a platform environment.
  • Config Server serves customer-service/sit from service and shared SIT overrides.
  • A database-backed service can be debugged from an IDE against forwarded SIT dependencies without duplicate processing.
  • Normal API validation remains through the API Gateway SIT port-forward.
  • Insomnia has Base Environment plus SIT, UAT, and PROD only.
  • UAT and PROD remain documented AWS targets with safe placeholders until provisioned.

Activity

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

    @ramioooz
    MemberAuthor

    Completed on 2026-08-04: the served configuration was migrated to SIT, workstation-to-SIT debugging was documented and validated, and Insomnia was aligned to Base, SIT, UAT, and PROD.

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