Skip to content
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 #2213

Closed
1 of 3 tasks
killianmuldoon opened this issue Aug 14, 2023 · 3 comments
Closed
1 of 3 tasks

Review hashicorp license change impact #2213

killianmuldoon opened this issue Aug 14, 2023 · 3 comments

Comments

@killianmuldoon
Copy link
Contributor

killianmuldoon commented Aug 14, 2023

Note: this issue is mostly being lead in core CAPI with this being a mirror issue for CAPV. The problems with both repos are the same, but more up to date info and disussion may be found at

Recently hashicorp announced changes to some of its licenses. This issue is a place to assess the impact on Cluster API Provider vSphere.

CNCF issue: cncf/foundation#617

None of the dependencies CAPV imports have been updated to the Business source license.

Initial findings

Generate list of all modules which are importing a hashicorp module.

go mod graph | grep "\s.*hashicorp" > hashicorp_modules

Get a unique sorted list of hashicorp modules that are being imported

cat hashicorp_modules | cut -d ' ' -f 2 | sort -u -o hashicorp_modules

The end result of the above is a list of 28 modules

@killianmuldoon
Copy link
Contributor Author

As in core CAPI we should consider doing license scans on PRs to identify license changes - initial PR for CAPI: kubernetes-sigs/cluster-api#9184

@killianmuldoon
Copy link
Contributor Author

IMO we can close this as done with the same rationale as kubernetes-sigs/cluster-api#9181

We can consider periodic image license scanning here too once the problem is solved in CAPI.

/close

@k8s-ci-robot
Copy link
Contributor

@killianmuldoon: Closing this issue.

In response to this:

IMO we can close this as done with the same rationale as kubernetes-sigs/cluster-api#9181

We can consider periodic image license scanning here too once the problem is solved in CAPI.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

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

No branches or pull requests

2 participants