fix(my-queries): add staging config COMPASS-9663 #7502
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR adds support for the atlas-staging environment configuration to resolve CORS issues preventing saved data functionality in the staging environment (cloud-stage.mongodb.com).
Key Changes:
- Added
atlas-stagingas a new backend preset option - Configured staging environment endpoints and authentication settings
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| packages/compass-preferences-model/src/preferences-schema.tsx | Added atlas-staging to the list of valid backend presets and updated documentation |
| packages/atlas-service/src/util.ts | Added complete staging environment configuration with API endpoints and OAuth settings |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| * - atlas-local: local mms backend (localhost) | ||
| * - atlas-dev: dev mms backend (cloud-dev.mongodb.com) | ||
| * - atlas-qa: qa mms backend (cloud-qa.mongodb.com) | ||
| * - atlas-staging: staging mms backend (cloud-stage.mongodb.com) |
There was a problem hiding this comment.
nit should we call it atlas-stage to mirror the actual env name?
There was a problem hiding this comment.
Good question lol, I've been meaning to get to the bottom of why it's called "stage" only for the MMS URL and it's called "staging" literally everywhere else
There was a problem hiding this comment.
I think "staging" is actually the more common name and "stage" is the exception
johnjackweir
left a comment
johnjackweir
left a comment
There was a problem hiding this comment.
one nit but not blocking
Description
Adding a config for cloud-stage.mongodb.com. Previously, this was preventing saved data from working in stage due to CORS issues.
Checklist
Motivation and Context
Open Questions
Dependents
Types of changes