-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Decide what to do w/ mapstructure library #9161
Comments
One of the options for existing forks: https://github.com/go-viper/mapstructure |
Trying to get #6671 fixed upstream and seeing how it goes could be a good test to see how receptive the new owners are to our use case |
I am offering that we switch over to the fork which will be maintained moving forward: #9634 |
**Description:** Update mapstructure to use a maintained fork, github.com/go-viper/mapstructure/v2. See mitchellh/mapstructure#349 for context **Link to tracking Issue:** #9161 Creating this as WIP to see if all tests pass.
Since we've taking the forked version can we close this issue? |
Will close it once we merge #9635, which fixes one of the things we were considering when tackling this issue |
The library is going to be deprecated and a few options for existing forks are coming up. Should we move to another fork, fork it ourselves?
See mitchellh/mapstructure#349
The text was updated successfully, but these errors were encountered: