-
Notifications
You must be signed in to change notification settings - Fork 883
feat: group provisioners by authentication method #14580
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
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.
So far so good! The UI looks really nice
I can go ahead and approve this now. Would you prefer that I do that, or wait until I get through all the other PRs first?
type, | ||
provisioners, | ||
}) => { | ||
const [provisioner] = provisioners; |
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.
Should there be a check to make sure that the provisioners
array isn't empty, or is that basically guaranteed not to happen?
If there are multiple provisioners, is there anything implied by the order they appear in? As in, is the first provisioner always the "main" one?
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.
currently, it should never be passed an empty provisioners
array, but I'm gonna refactor this to make it nicer.
site/src/pages/ManagementSettingsPage/OrganizationProvisionersPageView.stories.tsx
Show resolved
Hide resolved
site/src/pages/ManagementSettingsPage/OrganizationProvisionersPageView.tsx
Show resolved
Hide resolved
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.
Going to go ahead and approve
Closes #14459