You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently assigning a unique default data source name to each RuntimeConfig that we create. However, for a Hot Reload scenario this is problematic because we do not want to be updating this value after the Hot Reload, and so, it can not be uniquely generated each time.
Instead this value should be created in a deterministic way, ie: taking a hash of the connection string.
The text was updated successfully, but these errors were encountered:
…ading (#2069)
## Why make this change?
Closes#1967
We maintain the same default data source name after hot reloading.
## What is this change?
When hot reloading, pass along the original default data source name,
and after creating the runtimeconfig object, update that name and the
dependent data structures to use the original data source name from
before the hot reload.
## How was this tested?
- [ ] Unit Tests
Added validation that we maintain the same default data source name to
the unit tests.
## Sample Request(s)
- Example REST and/or GraphQL request to demonstrate modifications
- Example of CLI usage to demonstrate modifications
We are currently assigning a unique default data source name to each
RuntimeConfig
that we create. However, for a Hot Reload scenario this is problematic because we do not want to be updating this value after the Hot Reload, and so, it can not be uniquely generated each time.Instead this value should be created in a deterministic way, ie: taking a hash of the connection string.
The text was updated successfully, but these errors were encountered: