Migrating From Terraform To OpenTofu

OpenTofu is intended to be a drop-in replacement for HashiCorp Terraform. But is it? And why does it exist? And should you migrate? Those are some of the questions I wanted to answer in this week's Terraform Tuesday.
In the video we cover:
🌮 Why OpenTofu Exists
🌮 How to Migrate to OpenTofu
🌮 Whether You Should Migrate
Here are the links for everything I mentioned:
🔗 HashiCorp BSL Blog Post: www.hashicorp.com/blog/hashic...
🔗 HashiCorp Licensing FAQs: www.hashicorp.com/license-faq
🔗 OpenTofu Manifesto: opentofu.org/manifesto/
🔗 Comparison Blog Post: nedinthecloud.com/2024/01/22/...
🔗 Ephemeral Values prototype: github.com/hashicorp/terrafor...
🔗 OpenTofu Migration Guide: opentofu.org/docs/intro/migra...
🔗 Terraform Registry License: registry.terraform.io/terms
🔗 Day Two Cloud Episode 241: packetpushers.net/podcasts/da...
If I got something wrong please let me know!
Thank you so much for watching! Subscribe if you think I’ve earned it. Hit the bell as well if you’re feeling swell.❤️&🌮
✅🔔 Subscribe ► nedinthecloud.com/SubscribeYT
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
🌮 Other videos to check out:
📽️ Terraform Basics - Modules: • Terraform Basics: Modules
📽️ Managing Multiple Environments with Terraform: • Managing Multiple Envi...
📽️ Workload Identity with Terraform Cloud: • Using Workload Identit...
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
🌮 Timestamps:
⌚ 0:00 Intro
⌚ 1:11 Why OpenTofu Exists
⌚ 4:11 OpenTofu Current State
⌚ 6:40 Migrating To OpenTofu
⌚ 11:48 Migrating Back To Terraform
⌚ 12:18 Should You Migrate?
⌚ 14:40 Final thoughts
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
#terraform #hashicorp #devops #cloudengineer #azure #opentofu
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
⭐ CONNECT WITH ME 🏃🦖
🌐 Day Two Cloud: daytwocloud.io
🌐 Chaos Lever: chaoslever.com
🌐 Visit my Website ► nedinthecloud.com
🗳 Pluralsight ► app.pluralsight.com/profile/a...
🐙 Find the code at GitHub► github.com/ned1313
🐧 Twitter ► / ned1313
👨‍💼 LinkedIn► / ned-bellavance
For collaboration or any queries: [e-mail]
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
🌮 About Me 🌮
Ned is a curious human with a knack for creating entertaining and informative content. With over 20 years in the industry, Ned brings real-world experience to all his creative endeavours, whether that's pontificating on a podcast, delivering live instruction, writing certification guides, or producing technical training videos. He has been a helpdesk operator, systems administrator, cloud architect, and product manager. In his newest incarnation, Ned is the Founder of Ned in the Cloud LLC. As a one-man-tech juggernaut, he develops courses for Pluralsight, runs two podcasts (Day Two Cloud and Chaos Lever, and creates original content for technology vendors.
Ned has been a Microsoft MVP since 2017 and a HashiCorp Ambassador since 2020, and he holds a bunch of industry certifications that have no bearing on anything beyond his exceptional ability to take exams and pass them. When not in front of the camera, keyboard, and microphone, you can find Ned running the scenic trails of Pennsylvania or rocking out to live music in his hometown of Philadelphia. Ned has three guiding principles: Embrace discomfort, Fail often, and Be kind.

[@RahofAboRefaat-mr2mu]

You provide such valuable insights into tech transitions! 🌟 I'm eager to explore OpenTofu after your breakdown. Could you share a practical example of migrating a complex Terraform project to OpenTofu? I'd love to hear your experience on this!

[@NedintheCloud]

I don't have direct access to a large complex project at the moment. I'd say that the migration is fairly low risk. Make sure to back up your state data prior to making the switch and you should be pretty safe.

[@neilmcalister1310]

Nice vid Ned - thank you

[@vivekananadanramasubbu1542]

It is very informative. Thank you. I see opentofu uses azure provider from hashicorp. Is that fine ? Does it have any licence implications ?

[@ohad1282]

Yeah, opentofu uses all the existing providers. And BTW, the Azure provider is MPL.

[@MrMeneldor]

But if you are not currently using Terraform and search a tool for this job, should you start with Open Tofu ?

[@NedintheCloud]

Honestly, it doesn't really matter. From a training perspective, there's way more material out there for Terraform. Technically, OpenTofu and Terraform are functionally the same for 90% of the code base. The choice between them is mostly about licensing. If you think that BSL will apply to your use case (rare) then OpenTofu is probably the way to go. Otherwise, it's more a question of whether any features introduced since the fork are compelling to you.