Troubleshoot Stitch Webhook

[chadokruse]

• [x] Reach out to MongoDB team to troubleshoot server-side Stitch
• [x] Wait for MongoDB team response

Isolate M0 instance

• [x] Switch to M10 for one week
• [x] Switch back Monday Apr 15th

Isolate Axios/Webpack/Vue

• [x] Add simultaneous call to Google Cloud Function
• [x] Ensure Axios captures 502 errors (per MongoDB suggestion) UPDATE: It does capture

Note: Can reproduce Network Error using GCF created via Console. New requirements...

• [ ] Capture CORS issues in Bugsnag (currently just throws generic Network Error) [0]
• [x] Add crossdomain: true to Stitch Webhook Axios call

[0] Capturing CORS errors is not possible - for security purposes, browsers do not allow javascript to see pre-flight options request responses (link)

Isolate Axios

• [ ] Add side-by-side webhook using fetch

Isolate legacy Stitch app

• [ ] Create new MongoDB project w/ new M0 Atlas instance and new Stitch app

Isolate Stitch Origins Allowed

• [ ] Allow any origin Note: Vue is treating non-allowed origins as expected (i.e. Axios receives correct 'not allowed' response)

As a startup user, I want a place to get help so that I can continue exploring Stitch/Atlas without the expense of a support plan