-
Notifications
You must be signed in to change notification settings - Fork 184
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
sso: support multiple identity providers #212
Conversation
200b17c
to
c5a6983
Compare
Codecov Report
@@ Coverage Diff @@
## master #212 +/- ##
==========================================
- Coverage 62.34% 61.19% -1.15%
==========================================
Files 49 50 +1
Lines 4002 4069 +67
==========================================
- Hits 2495 2490 -5
- Misses 1352 1392 +40
- Partials 155 187 +32
|
85db1b6
to
31fb614
Compare
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.
This is great! 🔥
Below is a list of
|
Problem
We've been walking down the path to support multiple identity providers in several previous iterations. This last remaining stand is how to support configuration for multiple and different identity providers. The existing configuration structure is pretty inflexible and rigid when it comes to defining configuration, especially given our constraint to use environment variables.
We previously introduced
viper
to help solve some of these problems, but viper proved frustrating and lacking enough opinion to operate within. We roll that solution back here and instead use https://micro.mu/docs/go-config.htmlSolution
We introduced a new configuration component based on https://micro.mu/docs/go-config.html to build this new, more complicated configuration mechanism. This is a ground-up re-write of the configuration mechanism we use, found separately in
configuration.go
.Notes
This now looks like: