env0

There is nothing we appreciate more than kind words from our customers. 🙏 Listen to Troy E. Lillehoff, VP of Cloud Strategy, Architecture and Engineering at Western Union, describing how his team is using env0 to: ✅ Ensure consistent and secure infrastructure deployments ✅ Accelerate deployments through managed self-service ✅ Automate financial controls for effective cloud cost management and more!

Thank you The New Stack for having me on your podcast, talking about OpenTofu! https://lnkd.in/g22WTzaf

🐳 #Docker or #Kubernetes? Join 📦️ Jérôme Petazzoni, Docker original dev advocate, for a deep dive into container technologies, managing Kubernetes across multiple providers, unexpected IaC challenges and more! Tune in to our latest episode now👇

Yesterday, we shared our in-depth blog post detailing the upcoming release of OpenTofu v1.8. Now, let's break it down. We’re speeding towards the next stable release of OpenTofu, and you can already start testing it out! One of the most anticipated features in OpenTofu 1.8 is here: early evaluation of variables and locals. For years, #Terraform CLI users have been asking for the ability to use variables in the backend configuration block. This highly requested feature is now a reality in #OpenTofu! It makes your code more DRY (Don't Repeat Yourself) and coherent while reducing potential issues from workarounds. With OpenTofu 1.8.0-alpha1, you can use variables and locals to configure backends, module sources, and state encryption. As long as these variables or locals only depend on other variables, locals, or built-in functions, they are good to go! You can provide these variables during tofu init using the -var parameter or a variable file with -var-file. This is just the beginning!  Ready to dive in? - https://lnkd.in/ejjJWHet

Big news! OpenTofu 1.8 RC is here! 🎉 Arel Rabinowitz (env0 engineering, dev team OpenTofu) breaks it down for you: → Key features in 1.8 (The long-awaited early variable/locals evaluation has arrived!) → Practical use cases → How these changes will tackle existing challenges for OpenTofu users Read the full article 🔽

🚀 Exciting news! The first release candidate for 1.8.0 is here! 🌟 Check out the release here: https://lnkd.in/giEgBPBT 📑 These are the key updates of 1.8, if you are unaware: - 🛠️ Early Variable/Locals Evaluation: Utilize variables in backends, module sources, and more! This highly requested feature will greatly enhance flexibility in your tofu projects. - 📁 New .tofu File Extensions: Maintain compatibility with Terraform while taking advantage of new features exclusive to OpenTofu. - 🧪 Enhanced Testing Capabilities: Introducing override functionality in tofu test to better simulate environments during testing and mocking entire provider definitions 🔄 This is a rc release so your feedback is vital for perfecting the upcoming stable release. If you haven't already done so, join our community on Slack! https://opentofu.org/slack #OpenTofu #OpenSource 🚀✨

📥 Import existing console-created resources into your #Terraform / #OpenTofu code. Read this post to learn how to manage existing cloud resources without recreating them using the 'import' command👇

Déjà vu much? Tune into the full conversation with Zach Goldberg about #OpenTofu, #Terraform, and the future of open-source IaC: https://lnkd.in/dw5D7jg8

📘 For containerized applications, env0 tackles the critical task of provisioning the underlying infrastructure, encompassing both network and compute layers. This frees ArgoCD to focus solely on the application layer itself, fostering a clear separation of concerns. The initial step involves utilizing env0 to deploy #ArgoCD within the Kubernetes cluster. Notably, env0 offers Helm chart support, enabling the swift provisioning of new clusters pre-configured with ArgoCD alongside crucial services like cert-manager, ingress controllers, and metrics services. Following deployment, ArgoCD leverages its built-in Application CRD (Custom Resource Definition) to manage application deployments. By leveraging #Kubernetes manifests to define configurations, ArgoCD automates the application lifecycle, simplifying both installation and ongoing management. So, by deploying these application CRDs within env0, you can now introduce: - Access control - Approval workflows  - Approval policies through the deployment process - Management of 'time to live' This collaborative approach between env0 and ArgoCD facilitates efficient and controlled application deployment within Kubernetes. And what that means is you – as a platform engineering team or a DevOps team – you can now codify the entire application delivery process.

🗓️ Join our webinar on July 16 to learn how Rakuten Viber manages Infrastructure-as-Code across 800+ environments. Sergey Korolev and Andrew Way will share how mature IaC practices automate processes, improve developer experience, reduce technical debt, and streamline operations at scale. Sign up for free to learn real-world IaC strategies and best practices from industry experts! 👇