sso: introduce Viper for sso config management #196
Merged
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.
Problem
Although config management within SSO is fairly straightforward at the moment, it is also unorganised and doesn't leave much room for extension. Particularly in the sense of multi-provider workflows or for storing the config elsewhere (e.g. remote config). Fulfilling these workflows right now config wise is tricky.
Solution
Implement a new set of methods to manage config variables using a new package dependency such as Viper.
This PR currently introduces back-end changes that allow us to achieve this goal, while retaining functionality and flow (the same things are passed in, and the same things are returned).
Near-future PR's will include further changes to mould the usage of Viper to better fit our needs.