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
This issue is to discuss why for the multiple datasources feature the local cluster's id is ''. When implementing multiple datasources support for the security plugin, we realized that it is easy to confuse an empty string, with not passing in a variable. From a plugin developer perspective, it would be less confusing and error prone to have a different constant for the local cluster id, for example LOCAL or something equivalent. That way, when changing all the API calls to be multiple datasource compatible the caller needs to explicitly pass in LOCAL instead of if they forgot it defaults to the local cluster silently. Maybe there is some reason that I am not aware of why this decision was made.
From what I have seen, created datasource ids follow the format similar to '35c87960-00eb-11ef-98de-c373b609f89d', so anything not matching this format should work for the id of the local cluster, right?
The text was updated successfully, but these errors were encountered:
This issue is to discuss why for the multiple datasources feature the local cluster's id is
''
. When implementing multiple datasources support for the security plugin, we realized that it is easy to confuse an empty string, with not passing in a variable. From a plugin developer perspective, it would be less confusing and error prone to have a different constant for the local cluster id, for exampleLOCAL
or something equivalent. That way, when changing all the API calls to be multiple datasource compatible the caller needs to explicitly pass inLOCAL
instead of if they forgot it defaults to the local cluster silently. Maybe there is some reason that I am not aware of why this decision was made.From what I have seen, created datasource ids follow the format similar to '35c87960-00eb-11ef-98de-c373b609f89d', so anything not matching this format should work for the id of the local cluster, right?
The text was updated successfully, but these errors were encountered: