4 ms·
We have the tooling in place to ensure full equivalence of the most important parts, especially the statefile. We will also take great care to not introduce DSL
by fishnchips 3y ago
We have the tooling in place to ensure full equivalence of the most important parts, especially the statefile. We will also take great care to not introduce DSL changes that would make it hard to switch back and forth between OpenTF and the legacy Terraform. Looking at the codebase for the last week, and the list of PRs on the original repo ignored to oblivion I believe there's a lot of space for innovation that does not break the interop guarantee.
[Marcin, co-founder of Spacelift, one of the members of the OpenTF initiative]
- h1fra 3y agoThat's very nice to hear, thanks! (even though I wish there was some breaking changes to be able to fix some of nasty bugs that have been there for years ahah)
- freedomben 3y agoI think that's a good goal, but it seems pretty out of your hands. After your first addition to the language or state file (which by the sound of it is something you hope to do soon, and I applaud that), TF could immediately introduce something making compatibility impossible without you reverting and breaking the feature.
- fishnchips 3y agoThey could I guess, but with that they'd be abandoning support for all their previous versions, too. Plus it's software, there are a great many options here. I won't get into the nitty gritty not to spare everyone else the gruesome details but I'm not going to be losing sleep over this just now.