terraform-provider-azurerm VS sops

So this is doing my head in. Related to https://github.com/hashicorp/terraform-provider-azurerm/issues/6117

https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs

There are different Terraform Providers that enable Terraform to interact with Microsoft Azure. The most common one are Azure Stack, AzureDevops, AzureRM, AzAPI and AzureAD.. In this tutorial, we use the AzureRM Terraform Provider. Let's create a Terraform file for the AzureRM Terraform Provider.

Yeah we imported all the related resources. I could now find an issue, which exactly describes our problem. Unfortunately it is open since 2020: https://github.com/hashicorp/terraform-provider-azurerm/issues/8794

Like other people said, use the azurerm provider docs, they're pretty good. But that's where knowing Azure comes in handy because you'll have to figure out what TF resource to use to accomplish a given goal.

It’s not difficult at all syntactically. But you must understand the provider you are automating. So your azure knowledge is key in this case. Read the Azure provider docs and you will be easily able to put something together. https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs

My script just sets up default .sops.yaml for https://github.com/getsops/sops

You can further edit .sops.yaml(eg have multiple of them) and decide how you split secrets in your directory tree to further customize who can decrypt the secrets.

It works pretty well for prod/dev splits, etc

Mozilla SOPS (Secrets OPerationS) is an open-source command-line tool for managing and storing secrets. It uses secure encryption methods to encrypt secrets at rest and decrypt them at runtime. SOPS supports a variety of key management systems, including AWS KMS, GCP KMS, Azure Key Vault, and PGP. It's particularly useful in a DevOps context where sensitive data like API keys, passwords, or certificates need to be securely managed and seamlessly integrated into application workflows.

Encrypted secrets thanks to SOPS and Age

We do the exact same thing to keep track of some credentials we use sops[1] and AWS KMS to separate credentials by sensitivity, then use the git differ to view the diffs between the encrypted secrets

Definitely not best practice security-wise, but it works well

[1] https://github.com/getsops/sops

For anyone new to SOPS like I was - https://github.com/getsops/sops

I've found this is largely solved by strictly separating plain config and secrets, and then having secrets pull from GCP secret manager / vault / whatever.

You can then commit all the config (including the secret identifiers) and it all just works so long as you're authenticated with your secret storage system.

We do this for the live configuration as well in line with Gitops and find it to work well.

If you don't want to use a cloud secret manager you can also use something like https://github.com/getsops/sops to commit the encrypted secrets safely

Basically, the simpler the better --just encrypt your secrets and check them in to version control.

We use SOPS[0] for this, and have found it to be pretty nice.

[0]: https://github.com/getsops/sops

The answer is that secrets shouldn't be stored in the git repo at all, but somewhere safe like a password manager or Mozilla's SOPS which people seem to love.

Unfortunately, the SOPS project is in some sort of a limbo state and there has been quite a long period with limited maintenance and unclear position from Mozilla. Despite the project being accepted into the CNCF, it's still unclear what will happen with it going forward.