Skip to content

STORY: Maintain Insomnia workspace with SIT, UAT, and PROD environments #40

Closed

Description

@ramioooz

Create and maintain an Insomnia workspace that supports the platform delivery environments.

Environment model:

  • Base Environment: shared variable contract only, with no environment values or secrets.
  • SIT: the integrated platform deployed to local Kubernetes and exposed through a temporary API Gateway port-forward.
  • UAT: the future AWS-hosted user acceptance environment.
  • PROD: the future AWS-hosted production environment.

LOCAL-DEV is retired. Workstation debugging calls the temporarily local service port directly and is not an Insomnia deployment environment.

Definition of Done:

  • A Base Environment defines shared variable names without environment-specific secrets.
  • SIT, UAT, and PROD child environments exist.
  • Normal requests use apiGatewayUrl; direct downstream service URLs are not standard variables.
  • SIT uses http://localhost:8080 while the API Gateway port-forward is active.
  • UAT and PROD values are placeholders until deployed.
  • Credentials and tokens are not committed or exported.

Activity

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

    @ramioooz
    MemberAuthor

    Moved from Sprint 0 to Sprint 7 because its remaining definition of done is replacing and validating UAT and PROD endpoints after those environments are deployed. LOCAL-DEV and SIT requests remain covered by the gateway diagnostics story.

  4. changed the title [-]STORY: Create Insomnia workspace with LOCAL-DEV, SIT, UAT, and PROD environments[/-] [+]STORY: Maintain Insomnia workspace with SIT, UAT, and PROD environments[/+] on Aug 3, 2026
  5. ramioooz commented on Aug 31, 2026

    @ramioooz
    MemberAuthor

    Verified on 2026-08-31: the Insomnia workspace contains Base Environment plus SIT, UAT, and PROD. Normal requests use apiGatewayUrl, LOCAL-DEV and direct downstream service variables are not part of the standard environment model, and credentials/tokens are kept out of exported workspace data. The authentication/session follow-up is tracked separately by #48 and PR #178.

    This story is fulfilled; closing it as completed.

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