Skip to content
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

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

alepane21
Copy link
Contributor

@alepane21 alepane21 commented Nov 24, 2024

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

  • I have discussed my proposed changes in an issue and have received approval to proceed.
  • I have followed the coding standards of the project.
  • Tests or benchmarks have been added or updated.
  • Documentation has been updated on https://github.com/wundergraph/cosmo-docs.
  • I have read the Contributors Guide.

@alepane21 alepane21 marked this pull request as draft December 3, 2024 14:54
@alepane21 alepane21 marked this pull request as ready for review December 9, 2024 11:08
for _, ffConfig := range routerConfig.FeatureFlagConfigs.GetConfigByFeatureFlagName() {
for _, datasource := range ffConfig.EngineConfig.DatasourceConfigurations {
if customEvents := datasource.CustomEvents; customEvents != nil {
customEvents.DontVerify = true
Copy link
Contributor

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.

Copy link
Member

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

Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants