-
Notifications
You must be signed in to change notification settings - Fork 109
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
fix: provider should be specified in the config.yaml #1397
base: main
Are you sure you want to change the base?
fix: provider should be specified in the config.yaml #1397
Conversation
…oes-not-validate-schema-provider-id-is-valid-in-the
…-provider-id-is-valid-in-the
…oes-not-validate-schema-provider-id-is-valid-in-the
…-provider-id-is-valid-in-the
for _, ffConfig := range routerConfig.FeatureFlagConfigs.GetConfigByFeatureFlagName() { | ||
for _, datasource := range ffConfig.EngineConfig.DatasourceConfigurations { | ||
if customEvents := datasource.CustomEvents; customEvents != nil { | ||
customEvents.DontVerify = true |
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.
I'm not sure why we need this flag. It is also not the right way to extend the node_pb definition when this information is set at the router.
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.
+1 why do we need to disable this validation?
The only case is when you don't have edfs configuration at all, but then buildPubSub configuration won't be called
If we really need such an option I would suggest to name it differently - smth like
DisableEventProviderIdExistenceValidation
Just something more describing an intent of that option
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.
Create a separate graph configuration without the EDFS graph. In that case, you don't have to deal with cross-concern issues.
Motivation and Context
When the providers needed by the router are not configured the router should not start, but return an error.
The control should be disableable when necessary; on all old tests, the check is disabled.
Checklist