Fix/agent groups unique name migration#2786
Merged
greenbonebot merged 2 commits intomainfrom Feb 20, 2026
Merged
Conversation
timopollmeier
approved these changes
Feb 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Add database migration (268 to 269) to enforce UNIQUE(name) on agent_groups and agent_groups_trash.
Migrate existing data by appending the row ID to agent group names before adding the unique constraint.
Add validation logic to prevent creating or modifying agent groups with duplicate names.
Why
Previously, agent group names were not enforced as unique at the database level.
It is needed by the agent team for agent group identification.
References
GEA-1586