[macca321]

It'd be very interesting to know Hashi's internal strategy around this.

- Maybe do nothing, and as long as OpenTofu doesn't attempt to extend Terraform they are in not that different a position than pre-MPL.

- Add so many features OpenTofu can't keep up?

- Add some sneaky code to latest versions of hashi providers which makes them not work with unofficial terraform binaries?

[danw1979]

- You can imagine a situation where Tofu keeps TF DSL compatibility but add useful new features to the runtime (better plan summary, multiple stack deployment, chained deployments, etc). That’s going to put Hashicorp under pressure to move quicker..

- … but Hashicorp publicly pleaded poverty over their development resource on TF as the reason they wouldn’t accept community PRs. You can’t just grow a team tenfold overnight. They’ve been quite deliberate about the design of the Terraform language and runtime over the years, taking their time to add new features. It’s going to be interesting !

- The provider situation looks fairly safe to me. Those licenses didn’t change and you can always redirect to github releases for the really popular binaries ?

[fishnchips]

> multiple stack deployment, chained deployments

Intriguing ideas. Would you mind elaborating or - even better - open issues [0] explaining the concepts to gauge the community interest?

[0] https://github.com/opentofu/opentofu/issues