-
Notifications
You must be signed in to change notification settings - Fork 245
chore(compass-web): use ccs for atlas sandbox instead of local proxy COMPASS-8693 #6570
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
EDIT: CLOUDP-286880 is resolved, so should be able to proceed with this now |
|
Manually started a task to check that the test-web-with-atlas-cloud will pass as this task doesn't run on PRs automatically: https://spruce.mongodb.com/version/677f902afc201800075559d4/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC (it's green) |
| return electronProxyRemote; | ||
| } | ||
|
|
||
| debug('Waiting for x509 cert to propagate to Atlas clusters ...'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎊
|
|
||
| const WEBSOCKET_PROXY_PORT = process.env.COMPASS_WEBSOCKET_PROXY_PORT | ||
| ? Number(process.env.COMPASS_WEBSOCKET_PROXY_PORT) | ||
| : 1337; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤣
This patch switches the compass-web sandbox to use ccs instead of manually replicating the similar connection logic (creating a temp user and issuing a cert), this comes with two benefits: