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
At present, the dataSourceId schema validation for a route is lax in the sense that a dataSourceId when not present, it falls back to "Local Cluster".
This validation should be updated to check for hideLocalCluster flag. If the flag is set to false, then check if dataSourceId is present and a non-empty string.
The text was updated successfully, but these errors were encountered:
DarshitChanpura
changed the title
[Improvement] Use hideLocalCluster provided by cluster to determine whether a dataSourceId must be present
[Improvement] Use hideLocalCluster fflag to determine whether a dataSourceId must be present
Oct 16, 2024
DarshitChanpura
changed the title
[Improvement] Use hideLocalCluster fflag to determine whether a dataSourceId must be present
[Improvement] Use hideLocalCluster flag to determine whether a dataSourceId must be present
Oct 16, 2024
At present, the dataSourceId schema validation for a route is lax in the sense that a dataSourceId when not present, it falls back to "Local Cluster".
This validation should be updated to check for hideLocalCluster flag. If the flag is set to false, then check if dataSourceId is present and a non-empty string.
The text was updated successfully, but these errors were encountered: