mirror of
https://github.com/supabase/supabase.git
synced 2026-10-19 16:19:10 +03:00
Ivan VasilovandClaude Sonnet 5.5
cb17091d2d
## Problem New projects created on staging default to v2 (`cloud_provider: 'AWS'`). We want staging to start exercising v3 (`AWS_K8S`). Resolves FE-4640. ## Solution In `ProjectCreationForm`, the initial cloud provider is now rolled once per mount: on staging (`NEXT_PUBLIC_ENVIRONMENT === 'staging'`) it is `AWS_K8S` with 50% probability, otherwise the existing default. v3 is only rolled if the `infra:cloud_providers` custom content allows `AWS_K8S`. Prod and local are unchanged, and the internal-only "Cloud provider" selector still lets admins override the default. ## Review instructions 1. Run Studio with `NEXT_PUBLIC_ENVIRONMENT=staging` and the `newProjectInternalOnlyConfiguration` flag on. 2. Reload the new-project page several times and check that the "Cloud provider" select defaults to AWS and AWS (Revamped) about equally often. 3. Change the select manually and confirm the choice is kept and the project is created with it. 4. With `NEXT_PUBLIC_ENVIRONMENT=prod` or `local`, confirm the default is always AWS. ## Checklist - [x] I have read [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) - [ ] If I wrote a new docs topic or edited an existing topic, I used the `/write-the-docs` or `/edit-the-docs` skill, which applies the docs [style guide](https://github.com/supabase/supabase/tree/master/apps/docs/style-guide) 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>