We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Currently, data prepper does not validate that routes exist on startup, and even during runtime will not throw any errors.
To Reproduce Steps to reproduce the behavior: Create a config like
routes: - route_one: '/my_route == 10' - route_two: '/my_route == 11' sink: - pipeline: name: "sub-pipeline-1" routes: - FIRST_ROUTE - pipeline: name: "sub-pipeline-2" routes: - SECOND_ROUTE
None of the data will be routed to either pipeline, and there will be no errors or validations
Expected behavior Throw a validation error when a route is defined in the sink that does not exist. For the above, this may look like
Route "FIRST_ROUTE" does not exist. Configured routes include [resources_route, resource_route]
Screenshots If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Currently, data prepper does not validate that routes exist on startup, and even during runtime will not throw any errors.
To Reproduce
Steps to reproduce the behavior:
Create a config like
None of the data will be routed to either pipeline, and there will be no errors or validations
Expected behavior
Throw a validation error when a route is defined in the sink that does not exist. For the above, this may look like
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: