Skip to content

Stop validating agent lists #713

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

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

dodo920306
Copy link
Contributor

When serializers validate data, it compares them with the existing data in the DB for unique columns. Since agent lists are extracted from the DB, such validations will fail definitely. Thus, for getting data, the agent list in the response will skip for validation.

When serializers validate data, it compares them with the existing
data in the DB for unique columns. Since agent lists are extracted
from the DB, such validations will fail definitely. Thus, for getting
data, the agent list in the response will skip for validation.

Signed-off-by: dodo920306 <dodo920306@gmail.com>
@dodo920306 dodo920306 marked this pull request as draft July 15, 2025 13:37
@dodo920306
Copy link
Contributor Author

I want to figure out something first, so please don't merge this.

@dodo920306
Copy link
Contributor Author

@yeasy @YoungHypo Should agents actually be allowed to have the same name?
If there are 2 organizations naming their agents the same, they should be allowed to do it, right?

@yeasy
Copy link
Contributor

yeasy commented Jul 19, 2025

Agents will be in different namespaces based on the org. So one org cannot have two agents with the same name.

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

Successfully merging this pull request may close these issues.

3 participants