RCORE-2010 Update default base URL to new domain

[michael-wb]

What, How & Why?

Updated default base url to https://services.cloud.mongodb.com.
The default base url string value can be retrieved using App::default_base_url() static accessor or the realm_app_get_default_base_url() C_API function.

Fixes #7449

☑️ ToDos

• 📝 Changelog update
• 🚦 Tests (or not relevant)
• [ ] C-API, if public C++ API changed
• [ ] bindgen/spec.yml, if public C++ API changed

[coveralls-official]

Pull Request Test Coverage Report for Build michael.wilkersonbarker_1026

Details

• 36 of 36 (100.0%) changed or added relevant lines in 4 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.04%) to 92.147%

---

Totals
Change from base Build 2184:	0.04%
Covered Lines:	245396
Relevant Lines:	266309

---

💛 - Coveralls

[kraenhansen]

The properties key in the spec declare instance properties (implemented through instance methods on the C++ class), not static properties of the App: We currently don't have a way to expose static methods from C++ as static properties on the class, nor static properties directly.

Do you intent for SDKs to be able to set this value? I don't expect that to be the case, since it's a string_view. In fact, is there an SDK need to expose it at all?

If you want this to be exposed as a read-only static member of App, you'd need to conform to the style of the existing C++ code and express this as a static default_base_url function on App.

[michael-wb]

Thank you @kraenhansen - I have updated App::default_base_url to be a static accessor function (e.g. App::default_base_url()) - the purpose of this is to (hopefully) provide the default value to the SDKs so they don't have to define their own default base URL value.

[kraenhansen]

Until an SDK is actually expecting to consume this, I would suggest simply leaving it out of the spec.yml.

[michael-wb]

Sounds good - I will remove the reference until it is needed.

[mpobrien]

LGTM.
Since this is a "breaking" change, will it be a new major version of core? And if so, does that require that SDK releases which pull in that core version are published as new major versions?
In any case we'll need to communicate to any customers that might rely on domain whitelisting that by upgrading to an SDK that includes this change, they will need to either add the new set of domains to their whitelist, or explicitly set
the old https//realm.mongodb.com as their baseURL in the meantime.

[danieltabacaru]

In any case we'll need to communicate to any customers that might rely on domain whitelisting that by upgrading to an SDK that includes this change, they will need to either add the new set of domains to their whitelist, or explicitly set
the old https//realm.mongodb.com as their baseURL in the meantime.

As an alternative we could keep the default to https//realm.mongodb.com and the users have to explicitly set the new domain.

[melodeeli98]

As an alternative we could keep the default to https//realm.mongodb.com and the users have to explicitly set the new domain.

The App Services team requested this change so that migration to the new domains is as seamless as possible, especially with regards to users migrating to the new Private Endpoints. We decided that telling customers to upgrade their SDK versions would be easiest. The assumption was that any customers that experience issues with the new domain can choose to either stay in an older SDK version or override the base url themselves until they resolve their issues.

[michael-wb]

Thank you for the reply @melodeeli98!