terraform-provider-azurerm
sops
Our great sponsors
terraform-provider-azurerm | sops | |
---|---|---|
83 | 150 | |
4,397 | 15,069 | |
1.4% | 2.4% | |
10.0 | 9.2 | |
7 days ago | 9 days ago | |
Go | Go | |
Mozilla Public License 2.0 | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
terraform-provider-azurerm
- Private Endpoints as part of resource declaration
-
azurerm_linux_virtual_machine, datadisks and cloud-init
So this is doing my head in. Related to https://github.com/hashicorp/terraform-provider-azurerm/issues/6117
-
A Step-by-Step Guide on Creating a Resource Group, Virtual Network and Subnet in Azure with Terraform.
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs
- 409 Error in creating Azure diagnostic setting
-
How to Set Up an Azure Kubernetes Service Cluster with Terraform
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.
-
Azurerm Import Windows Virtual Machine into statefile
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
- Update routing intent on Virtual WAN with AzAPI
-
How to get started with Terraform for Azure?
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.
-
How hard is terraform to learn?
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
sops
-
Pico.sh – Hacker Labs
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
-
Encrypting your secrets with Mozilla SOPS using two AWS KMS Keys
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.
-
An opinionated template for deploying a single k3s cluster with Ansible backed by Flux, SOPS, GitHub Actions, Renovate, Cilium, Cloudflare and more!
Encrypted secrets thanks to SOPS and Age
-
Tracking SQLite Database Changes in Git
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
-
The Twelve-Factor App
For anyone new to SOPS like I was - https://github.com/getsops/sops
- Storing and managing private keys
-
Show HN: Shello – Wrangle Environment Variables
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
-
Check your secrets into Git [video]
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
-
How to secure secrets of docker-compose stacks with git?
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.
-
Is it safe to commit a Terraform file to GitHub?
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.
What are some alternatives?
terraform-provider-azuread - Terraform provider for Azure Active Directory
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
terraform-provider-grafana - Terraform Grafana provider
Vault - A tool for secrets management, encryption as a service, and privileged access management
AdGuardHome - Network-wide ads & trackers blocking DNS server
age - A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
terraform-provider-lastpass - Terraform Lastpass provider
git-crypt - Transparent file encryption in git
buildah - A tool that facilitates building OCI images.
terraform-provider-sops - A Terraform provider for reading Mozilla sops files
tfsec - Security scanner for your Terraform code [Moved to: https://github.com/aquasecurity/tfsec]
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.