adyxax/www
1
0
Fork 0
Code Issues Activity

capitalize OpenTofu

Browse source
This commit is contained in:
Julien Dessaux 2024-10-02 08:51:29 +02:00
parent 27e8b4499c
commit d7e37eea52
Signed by: adyxax
GPG key ID: F92E51B86E07177E
8 changed files with 26 additions and 26 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
content/blog/aws/defaults.md
View file

@ -1,10 +1,10 @@
---
title: Securing AWS default VPCs
description: With terraform/opentofu
description: With terraform/OpenTofu
date: 2024-09-10
tags:
- aws
- opentofu
- OpenTofu
- terraform
---

4
content/blog/aws/secrets.md
View file

@ -1,10 +1,10 @@
---
title: Managing AWS secrets
description: with the CLI and with terraform/opentofu
description: with the CLI and with terraform/OpenTofu
date: 2024-08-13
tags:
- aws
- opentofu
- OpenTofu
- terraform
---

6
content/blog/cloudflare/importing-terraform.md
View file

@ -1,16 +1,16 @@
---
title: Importing cloudflare DNS records in terraform/opentofu
title: Importing cloudflare DNS records in terraform/OpenTofu
description: a way to get the records IDs
date: 2024-07-16
tags:
- cloudflare
- opentofu
- OpenTofu
- terraform
---
## Introduction
Managing cloudflare DNS records using terraform/opentofu is easy enough, but importing existing records into your automation is not straightforward.
Managing cloudflare DNS records using terraform/OpenTofu is easy enough, but importing existing records into your automation is not straightforward.
## The problem

6
content/blog/terraform/acme.md
View file

@ -1,16 +1,16 @@
---
title: Certificate management with opentofu and eventline
title: Certificate management with OpenTofu and eventline
description: How I manage for my personal infrastructure
date: 2024-03-06
tags:
- Eventline
- opentofu
- OpenTofu
- terraform
---
## Introduction
In this article, I will explain how I handle the management and automatic renewal of SSL certificates on my personal infrastructure using opentofu (the fork of terraform) and [eventline](https://www.exograd.com/products/eventline/). I chose to centralise the renewal on my single host running eventline and to generate a single wildcard certificate for each domain I manage.
In this article, I will explain how I handle the management and automatic renewal of SSL certificates on my personal infrastructure using OpenTofu (the fork of terraform) and [eventline](https://www.exograd.com/products/eventline/). I chose to centralise the renewal on my single host running eventline and to generate a single wildcard certificate for each domain I manage.
## Wildcard certificates

2
content/blog/terraform/caa.md
View file

@ -3,7 +3,7 @@ title: CAA DNS records with OpenTofu
description: How I manage which acme CA can issue certificates for me
date: 2024-05-27
tags:
- opentofu
- OpenTofu
- terraform
---

8
content/blog/terraform/chart-http-datasources.md
View file

@ -1,18 +1,18 @@
---
title: Manage helm charts extras with opentofu
title: Manage helm charts extras with OpenTofu
description: a use case for the http datasource
date: 2024-04-25
tags:
- aws
- opentofu
- OpenTofu
- terraform
---
## Introduction
When managing helm charts with opentofu (terraform), you often have to hard code correlated settings for versioning (like app version and chart version). Sometimes it goes even further and you need to fetch a policy or a manifest with some CRDs that the chart will depend on.
When managing helm charts with OpenTofu (terraform), you often have to hard code correlated settings for versioning (like app version and chart version). Sometimes it goes even further and you need to fetch a policy or a manifest with some CRDs that the chart will depend on.
Here is an example of how to manage that with opentofu and an http datasource for the AWS load balancer controller.
Here is an example of how to manage that with OpenTofu and an http datasource for the AWS load balancer controller.
## A word about the AWS load balancer controller

4
content/blog/terraform/email-dns-unused-zone.md
View file

@ -1,11 +1,11 @@
---
title: Email DNS records for zones that do not send emails
description: Automated with terraform/opentofu
description: Automated with terraform/OpenTofu
date: 2024-09-03
tags:
- cloudflare
- DNS
- opentofu
- OpenTofu
- terraform
---

18
content/blog/terraform/tofu.md
View file

@ -1,20 +1,20 @@
---
title: Testing opentofu
title: Testing OpenTofu
description: Little improvements and what it means for small providers like mine
date: 2024-01-31
tags:
- Eventline
- opentofu
- OpenTofu
- terraform
---
## Introduction
This January, the opentofu project announced the general availability of their terraform fork. Not much changes for now between terraform and opentofu (and that is a good thing!), as far as I can tell the announcement was mostly about the new provider registry and of course the truly open source license.
This January, the OpenTofu project announced the general availability of their terraform fork. Not much changes for now between terraform and OpenTofu (and that is a good thing!), as far as I can tell the announcement was mostly about the new provider registry and of course the truly open source license.
## Registry change
The opentofu registry already has all the providers you are accustomed to, but your state will need to be migrated with:
The OpenTofu registry already has all the providers you are accustomed to, but your state will need to be migrated with:
```sh
tofu init -upgrade`
```
@ -24,19 +24,19 @@ For some providers you might encounter the following warning:
- Installed cloudflare/cloudflare v4.23.0. Signature validation was skipped due to the registry not containing GPG keys for this provider
```
This is harmless and will resolve itself when the providers' developers provide the public GPG key used to sign their releases to the opentofu registry. The process is very simple thanks to their GitHub workflow automation.
This is harmless and will resolve itself when the providers' developers provide the public GPG key used to sign their releases to the OpenTofu registry. The process is very simple thanks to their GitHub workflow automation.
## Little improvements
- `tofu init` seems significantly faster than `terraform init`.
- You never could interrupt a terraform plan with `C-C`. I am so very glad to see that it is not a problem with opentofu! This really needs more advertising: proper Unix signal handling is like a superpower that is too often ignored by modern software.
- `tofu test` can be used to assert things about your state and your configuration. I did not play with it yet but it opens [a whole new realm of possibilities](https://opentofu.org/docs/cli/commands/test/)!
- You never could interrupt a terraform plan with `C-C`. I am so very glad to see that it is not a problem with OpenTofu! This really needs more advertising: proper Unix signal handling is like a superpower that is too often ignored by modern software.
- `tofu test` can be used to assert things about your state and your configuration. I did not play with it yet but it opens [a whole new realm of possibilities](https://OpenTofu.org/docs/cli/commands/test/)!
- `tofu import` can use expressions referencing other values or resources attributes, this is a big deal when handling massive imports!
## Eventline terraform provider
I did the required pull requests on the [opentofu registry](https://github.com/opentofu/registry) to have my [Eventline provider](https://github.com/adyxax/terraform-provider-eventline) all fixed up and ready to rock!
I did the required pull requests on the [OpenTofu registry](https://github.com/OpenTofu/registry) to have my [Eventline provider](https://github.com/adyxax/terraform-provider-eventline) all fixed up and ready to rock!
## Conclusion
I hope opentofu really takes off, the little improvements they made already feel like a breath of fresh air. Terraform could be so much more!
I hope OpenTofu really takes off, the little improvements they made already feel like a breath of fresh air. Terraform could be so much more!