#opentofu — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #opentofu, aggregated by home.social.
-
Why #cloudformation is so bad? Especially when I want to remove the stack without removing resources...
-
One day I should add CI to my Terraform/OpenTofu infrastructure repository, so I can apply changes from my phone while sitting in a train :3
Just gotta figure out a better way of managing secrets and state for that.Also, can't wait to break my CI by updating the infrastructure and then being unable to remotely fix it xD
#Terraform #OpenTofu #self-hosting #IaC -
CVE Alert: CVE-2024-58375 - opentofu - opentofu - https://www.redpacketsecurity.com/cve-alert-cve-2024-58375-opentofu-opentofu/
#OSINT #ThreatIntel #CyberSecurity #cve-2024-58375 #opentofu #
-
Nova atividade para o CoffeeOps de Agosto no LHC. Dia 15 de às 09:00 horas
Agora vamos falar de Proxmox IaC: Gerenciamento com OpenTofu & Terraform com o Marc Pires.
Uma apresentação mão na massa sobre gerenciamento do Procmox com IaC
Tópicos:
Proxmox API
Preparando o ambiente com Terraform/OpenTofu e SeeWeedFS
Preparando Proxmox
Criando VMS e outros recursos via IaChttps://eventos.lhc.net.br/event/coffeeops-2026-08
#hackerspace #coffeeops #comunidade #proxmox #iac #campinas #cafe #free #opentofu #terraform #devops
-
Looks like it works! Finally Terraform Provider that works with Zabbix 7.0. I wished for this for more than a year.
-
I moved cichyform repository with my custom Terraform modules to @codefloe . Original repository on codeberg has not been deleted but archived so your stacks should be usable without any migrations. But all tags and commits are migrated to CodeFloe, so just simple edit in source="" should be enough to migrate :-)
-
Ang. min förra boost: #Stacikit är ett intressant(europeiskt) alternativ till #Azure och #AWS. För två år sen var deras utbud inte stort men nu har det utökats med AI-orkestrering, K8s, CRs, Messaging, mm. Mycket av det ser ut att bygga på Open Source. Det finns även stöd för #Terraform(borde även fungera med #OpenTofu).
-
👋 Je propose une mission DevSecOPS pour construire la plateforme d'hébergement de la DINUM qui accueille les applications de l'État, vous travaillez sur les couches d'accès (Coeur de réseau, Load Balancer, VPN, Pare-Feu, Proxy ainsi que leur durcissement du système). La plateforme est construite sur des offres IaaS Interne à l'État ou des clouds SecNumCloud.
Plus d'infos ici :
https://docs.numerique.gouv.fr/docs/50d6dc53-aa9e-4970-b79a-dbab6843b279/#OpenTofu #Terraform #DevOPS #Indep
Merci pour les repouets !
-
I wiped my homelab and got it up and running again in 5 minutes. I used what I like to call the BAT stack which is Bootc, Ansible, and Terraform. Bootc for image based os builds, Ansible for configuration, and Terraform for VM provisioning on Proxmox. All being versioned controlled.
Check out more on my blog
https://keijilohier.com/blogs/recreating-my-homelab-with-infrastructure-as-code/
#homelab #bootc #ansible #terraform #proxmox #git
#iac #opentofu -
Ok, one more but it goes with 2. : DO NOT configure your providers in the #terraform / #opentofu code. You're shooting yourself in the foot here, let #terragrunt handle this dynamically.
-
The more I work as a Dev Ops / Platform Eng, the more I fight a single anti-pattern.
For your future self :
1. Use #terragrunt and not only #terraform / #opentofu ,
2. Centralize you #tf code in different modules in a single repository and have #tg use them ,
3. That one goes without saying but here it is : DRY your code using locals !I'm tired of removing hundred lines of #IaC code just for the sake of maintainability.
-
@sharlatan you're evaluating Mitchell instead of whether a approach similar to vouch would be useful for guix.
fwiw - I made a minor contribution to terraform pre the BSL change..not happy about the license change, but atleast we have #opentofu
I don't think that Mitchel had decision making authority in the terraform BSL change (not in a leadership position when the decision was made afaik). I also am not familiar the his exit from hashicorp; perhaps you're a little hard on him here? 🤷♂️
-
Tak to wygląda w module w templatce #butane oraz wywoałeni w stacku środowiska w #terraform / #opentofu
-
Just discovered that #Terraform supports #Proxmox... might be a nice lil weekend project - importing my Proxmox config into Terraform lol. I feel like that makes more sense than smtg like #Ansible right?
---
edit: as per someone's rec, #OpenTofu may be a like-for-like better choice instead of Terraform -
#OpenTofu 1.12 is out!
This update isn’t a complete rewrite, but it does resolve some issues that infrastructure teams have faced for a while.
Find out more: https://bit.ly/3RY6AdU
-
OpenTofu continua a crescere come piattaforma Infrastructure as Code open source compatibile con Terraform. Nuove funzioni semplificano multi-cloud, sicurezza e gestione dei provider. #OpenTofu #Linux #DevOps #CloudComputing #Terraform #InfrastructureAsCode
-
OpenTofu 1.12 IaC tool adds dynamic prevent_destroy support, provider checksum improvements, faster installs, and CLI output updates.
https://linuxiac.com/opentofu-1-12-iac-tool-adds-dynamic-prevent_destroy-support/ -
Follow-up on #Forgejo vs #Gitea:
I read more about the split, and I'm still not sure.
I understand the governance concerns around Gitea, and Forgejo’s FOSS/community direction is very appealing.
But #Gitea supports #OpenTofu state, which I need, and I don't think "open source + paid hosting/support" is a bad model. Actually, it can be one of the healthier ways to fund development.
Maintainers should be paid. Good open-source tools need time, money, and boring long-term maintenance.
-
Yay!! 2k GitHub stars 🎉
Will celebrate with a new release 🤘
#Terraform #OpenTofu #Proxmox #bpg -
OpenTofu vs Terraform in 2026: the fork finally diverged
https://jorijn.com/en/blog/opentofu-vs-terraform-2026-the-fork-finally-diverged/
-
Well, that was weird. I was hired to help a client with build an internal #Kubernetes as-a-service solution, but ended up designing and deploying a new #PowerDNS setup for them instead. Client is happy. They managed to hire a full time employee to cover my spot, so it ends up being a short 3 month contract, which is done in one.
Coming out of a very convenient and comfortable series of contracts for a single client, totalling six years, this is very different. This is the first client who's mentioned #AI (and been rather excited about it) so I'm playing catch up and trying to establish my position on that. I'm guessing there will soon be a huge market for sensible adult contractors, ready to clean up after AI #slop spills. Time will tell.
Anyhoo, my network seems to have my back as usual, and I've got some interviews coming up in the following weeks. Trying to focus on gigs using Kubernetes, #Terraform, #OpenTofu and #Go, which means saying "no thanks" a lot. That's new for me.
#work -
Let's continue the Proxmox + Tofu + Talos + Cilium adventure, with two little footnotes. "Devil is in the details!"
First: Talos "inlineManifests" behavior.
When you add some inlineManifests to your Talos MachineConfig and push that MachineConfig, the manifests get applied immediately. Yay!
However, when you update or remove some inlineManifests and push the MachineConfig ... Nothing happens. Talos does a full (potentially destructive!) reconcile only when executing a cluster upgrade. (This is pretty well explained in the Talos docs[1])
This means that our initial installation of CIlium will work immediately, but subsequent configuration changes won't work (the YAML won't be applied) until we run a "talosctl upgrade-k8s". (Pro-tip: make sure to specify "--to" with the current k8s version, otherwise it'll execute a "real" upgrade which implies downloading new images and restarting the whole control plane one component at a time - which takes a while.)
So, are we there yet?
Not quite!
The second issue: each time I'd do a "tofu plan", it would tell me that something had changed. Which is kind of annoying. If you don't change your Tofu configuration, variables, etc, normally, you'd expect "tofu plan" to tell you a reassuring:
No changes. Your infrastructure matches the configuration.
So, what is going on? 🤔