Skip to content

PLAT-004: Independent Multi-Deployment

Statement

The system shall support multiple independent deployments of the Shifter platform. Each deployment shall operate as a fully isolated instance with its own application services, database, users, content, and range infrastructure. Deployments shall share no runtime state, data, or infrastructure with other deployments. Each deployment shall be independently upgradeable, configurable, and operable.

Rationale

Multiple independent deployments enable Shifter to serve different organizations, regions, or security boundaries without co-tenancy risk. Each deployment can be sized, configured, and managed according to its specific operational requirements. Isolation ensures that an outage, misconfiguration, or security incident in one deployment cannot affect another.

Traceability

  • IMPLEMENTS → CONFIG shifter/shifter_platform/config/settings.py (Closed runtime settings resolved for each deployment)
  • IMPLEMENTS → CONFIG platform/terraform/environments/ (Independent AWS environment roots and deployment configuration)
  • DOCUMENTS → GITHUB_ISSUE Brad-Edwards/bigrae#673 (PLAT-004: Independent Multi-Deployment)
  • IMPLEMENTS → CONFIG platform/terraform/environments/dev/main.tf (Independent AWS dev deployment environment)
  • IMPLEMENTS → CONFIG platform/terraform/environments/prod/main.tf (Independent AWS prod deployment environment)
  • IMPLEMENTS → CONFIG platform/terraform/gcp/environments/platform/main.tf (Shared GCP environment root with explicit per-deployment project and settings)