-
Notifications
You must be signed in to change notification settings - Fork 18
Update data-governance.mdx #574
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
base: master
Are you sure you want to change the base?
Conversation
Deploying configcat-docs with
|
Latest commit: |
4e3ab65
|
Status: | ✅ Deploy successful! |
Preview URL: | https://ef152042.docs-xmy.pages.dev |
Branch Preview URL: | https://aisz0811-patch-6.docs-xmy.pages.dev |
@@ -44,10 +42,10 @@ in your application code when it is being initialized. | |||
|
|||
## Troubleshooting | |||
|
|||
#### What if I forgot to pass the `dataGovernance` parameter? | |||
#### What happens if I forget to pass the `dataGovernance` parameter? | |||
|
|||
The ConfigCat backend will take the Dashboard preference as primary. Having `EU Only` selected on the Dashboard but forgot to pass the proper `dataGovernance` parameter to the SDK. In this case your config JSONs will only published to the EU CDN nodes. And every config JSON download made from your application to any node outside the EU, the request will be redirected automatically to the EU CDN. Recommended to deploy a fix with the correct `dataGovernance` param, since response times will be significantly longer. |
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 section could be improved too as it's pretty incoherent and hard to follow.
@@ -44,10 +42,10 @@ in your application code when it is being initialized. | |||
|
|||
## Troubleshooting | |||
|
|||
#### What if I forgot to pass the `dataGovernance` parameter? | |||
#### What happens if I forget to pass the `dataGovernance` parameter? | |||
|
|||
The ConfigCat backend will take the Dashboard preference as primary. Having `EU Only` selected on the Dashboard but forgot to pass the proper `dataGovernance` parameter to the SDK. In this case your config JSONs will only published to the EU CDN nodes. And every config JSON download made from your application to any node outside the EU, the request will be redirected automatically to the EU CDN. Recommended to deploy a fix with the correct `dataGovernance` param, since response times will be significantly longer. | |||
|
|||
#### `Warning: Your dataGovernance parameter at ConfigCatClient initialization is not in sync with your preferences...` |
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 warning message has changed, see also https://docs.google.com/spreadsheets/d/1twC9G40PQK7cmUXTAVEgNMvDdFJxoN9W6WTLOU9wRM4/edit?usp=sharing
#### `Warning: Your dataGovernance parameter at ConfigCatClient initialization is not in sync with your preferences...` | |
#### `Warning: The dataGovernance parameter specified at the client initialization is not in sync with the preferences on the ConfigCat Dashboard....` |
Co-authored-by: adams85 <[email protected]>
Describe the purpose of your pull request
Related issues (only if applicable)
How to test? (only if applicable)
Requirement checklist