-
Notifications
You must be signed in to change notification settings - Fork 444
Fix fail to access the agent list #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
Fix fail to access the agent list #713
Conversation
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 <[email protected]>
|
I want to figure out something first, so please don't merge this. |
|
@yeasy @YoungHypo Should agents actually be allowed to have the same name? |
|
Agents will be in different namespaces based on the org. So one org cannot have two agents with the same name. |
This reverts commit 849e071. Signed-off-by: dodo920306 <[email protected]>
Agents don't have to be given different names. They will work under their own organization respectively, so it's unnecessary to restrict their name duplication. Signed-off-by: dodo920306 <[email protected]>
f5753c9 to
6690d89
Compare
One organization can't have multiple agents, so in the end, there is no need to keep agent names unique. |
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.