-
Notifications
You must be signed in to change notification settings - Fork 907
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
Review hashicorp license change impact #3941
Comments
Thanks @chaunceyjiang, I'm looking at this now. Just trying to state the current situation. We are using # go mod why github.com/hashicorp/hcl
# github.com/hashicorp/hcl
github.com/karmada-io/karmada/hack/tools
github.com/vektra/mockery/v2 // requires github.com/spf13/viper (https://github.com/vektra/mockery/blob/8abb7022eefaf0d424283d8957117e31e6eaa1cf/go.mod#L14C32-L14C32)
github.com/vektra/mockery/v2/cmd
github.com/spf13/viper // requires github.com/hashicorp/hcl (https://github.com/spf13/viper/blob/b77f4c19280bab64272eb8dba6c3a15bb2cae0ce/go.mod#L7C13-L7C22)
github.com/spf13/viper/internal/encoding/hcl
github.com/hashicorp/hcl So the chain is that:
Let's see if viper could get rid of |
Just a quick update: After that, we still need to wait for mockery to integrate the new version of viper. |
/kind cleanup |
/remove-kind bug |
What happened:
Recently hashicorp announced changes to some of its licenses. This issue is a place to assess the impact on Karmada.
CNCF issue: cncf/foundation#617
What you expected to happen:
None of the dependencies Karmada imports have been updated to the Business source license.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl-karmada version
orkarmadactl version
):The text was updated successfully, but these errors were encountered: