-
Notifications
You must be signed in to change notification settings - Fork 887
feat: add display_name field to groups #8740
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
Conversation
This is a non-unique human friendly group name for display purposes. This means a display name can be used instead of using an environment var to remap groups with OIDC names to Coder names. Now groups can retain the OIDC name for mapping, and use a display name for display purposes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good overall, I don't see any tests in post/patch
for enterprise/coderd
though.
I'll add to the existing tests |
I added onto the existing patch/create tests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would probably be good to add a test in cli
too since we're supporting it there.
What this does
Adds an optional non-unique human friendly group name for display purposes. This is required for #8214. This essentially allows mapping a non-friendly group name to a friendly one at runtime, rather than
OIDC_GROUP_MAPPING
(which requires a restart).This field defaults to the empty string (""). By default
name
is used as the display name. So this features changes nothing about how groups currently work.If the
display_name
is set however, then that name takes priority for the UI.