Skip to content

Conversation

tklauser
Copy link
Member

@tklauser tklauser commented Apr 8, 2025

The github.com/mitchellh/mapstructure package is archived and no longer receives updates1. The "blessed" fork2 is github.com/go-viper/mapstructure. The API is the same, so nothing needs to be changed apart from the import path.

Footnotes

  1. https://github.com/mitchellh/mapstructure/issues/349

  2. https://gist.github.com/mitchellh/90029601268e59a29e64e55bab1c5bdc

The github.com/mitchellh/mapstructure package is archived and no
longer receives updates[^1]. The "blessed" fork[^2] is
github.com/go-viper/mapstructure. The API is the same, so nothing needs
to be changed apart from the import path.

[^1]: mitchellh/mapstructure#349
[^2]: https://gist.github.com/mitchellh/90029601268e59a29e64e55bab1c5bdc

Signed-off-by: Tobias Klauser <tobias@cilium.io>
@tklauser tklauser requested a review from a team as a code owner April 8, 2025 15:43
@tklauser tklauser requested review from dylandreimerink and removed request for a team April 8, 2025 15:43
@tklauser tklauser enabled auto-merge (rebase) April 8, 2025 15:45
@tklauser tklauser merged commit 8eacab6 into main Apr 9, 2025
1 check passed
@tklauser tklauser deleted the pr/tklauser/mapstructure-blessed-fork branch April 9, 2025 15:09
@joamaki
Copy link
Contributor

joamaki commented May 22, 2025

Unfortunately go-viper/mapstructure is not compatible due to go-viper/mapstructure#6. We saw the same issue in cilium/cilium#30028. I'm going to revert this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants