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

[BUG] Validate for existing name when creating detector #207

Open
amsiglan opened this issue Dec 21, 2022 · 1 comment
Open

[BUG] Validate for existing name when creating detector #207

amsiglan opened this issue Dec 21, 2022 · 1 comment
Labels
backport 2.x bug Something isn't working

Comments

@amsiglan
Copy link
Collaborator

What is the bug?
When user creates a detector, we are not verifying if a detector with same name already exists.

How can one reproduce the bug?
Steps to reproduce the behavior:

  1. Create a detector using create detector API
  2. Create another detector with same name

What is the expected behavior?
API fails to created the second detector with error along the lines of detector with same name already exists

What is your host/environment?
NA

Do you have any screenshots?
Na

Do you have any additional context?
NA

@amsiglan amsiglan added bug Something isn't working untriaged labels Dec 21, 2022
@getsaurabh02 getsaurabh02 added backport 2.x v2.5.0 2.5.0 release and removed untriaged labels Dec 21, 2022
@sbcd90
Copy link
Collaborator

sbcd90 commented Jan 6, 2023

@raj-chak assigned to you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 2.x bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants