You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Change of Hashicorp license from open source MPL to BSL for terraform.
Problem of using TF alternatives with Terraform Registry since changes in Terraform Registry terms.
Describe the solution you'd like
Nothing yet, just describing the issue and starting discussion if the author or other people missed above event.
Using this provider with OpenTF in the future would be nice option (for this to be fair with Terraform Registry and legal, it would probably need to use additional registry other than from HashiCorp, see 3rd link below)
This is an interesting development indeed. I don't fully understand yet how BSL for terraform and new terms for HashiCorp's TF registry affect providers.
Personally I would not consider adopting anything other than an open source license.
Now I'm also considering to include DCO to all contributions as well.
Is your feature request related to a problem? Please describe.
Change of Hashicorp license from open source MPL to BSL for terraform.
Problem of using TF alternatives with Terraform Registry since changes in Terraform Registry terms.
Describe the solution you'd like
Nothing yet, just describing the issue and starting discussion if the author or other people missed above event.
Using this provider with OpenTF in the future would be nice option (for this to be fair with Terraform Registry and legal, it would probably need to use additional registry other than from HashiCorp, see 3rd link below)
Describe alternatives you've considered
.
Additional context
The text was updated successfully, but these errors were encountered: