Terraform
Terraform can manage existing and popular service providers, such as AWS, as well as custom in-house solutions.
It uses configuration files to describe the components necessary to run a single application or your entire datacenter.
It generates an execution plan describing what will happen to reach the desired state, and afterwards executes it to build the desired infrastructure. As the configuration changes, Terraform is able to determine the changes and create incremental execution plans which can be applied.
The infrastructure Terraform can manage includes low-level components such as compute instances, storage, and networking, as well as high-level components such as DNS (Domain Name Service) entries, SaaS (Software as a Service) features.
Here are 11,829 public repositories matching this topic...
Add basic CI
We already have some scripts in the scripts directory. It would be good to run them for every PR.
This is also a great task for beginners.
## Python/Regex fix
I suggest adding MongoDB Atlas to the supported cloud as a feather.
General Availability (GA) for docker compose v2 is "Almost There". With GA we could consider upgrading docker compose examples (sample project and [test](https://github.com/
Currently, terragrunt hclfmt will tell you if there are errors with your hcl file, but not display what they are if you are using --terragrunt-check flag. Example:
terragrunt hclfmt --terragrunt-check --terragrunt-log-level error
terraform fmt has this functionality with the -diff switch to show you what changes it would end up doing, which is great for CI and the end-user feedback l
-
Updated
Nov 23, 2021
Here are the steps to migrate a resource:
- Pull latest changes from my
refactor-migration-t1branch. - Set the var
SINGLE_RESOURCE_NAMEincmd/migrator/main.goto the resource filename. - Run
go run cmd/migrator/main.go, the resource file would be edited and a new resource file will be created ininternal/resources/aws - All things that the script was unable to migrate are chang
-
Updated
Jan 24, 2022 - Go
Manually keeping all dependencies up to date can be a time consuming task which can easily be automated.
One possible solution for this is renovatebot which periodically checks for new versions and can create a pull request for each update found.
It can easily be deployed on kubernetes via helm and works with [gite
-
Updated
Dec 27, 2021 - Shell
-
Updated
Jan 24, 2022 - Go
Describe the issue
https://github.com/bridgecrewio/checkov/blob/master/checkov/dockerfile/checks/UserExists.py doesn't cover all of https://docs.bridgecrew.io/docs/ensure-that-a-user-for-the-container-has-been-created
Bridgecrew Policy ID: BC_DKR_3
Checkov Check ID: CKV_DOCKER_3
ToDo: Additionally check if gosu is executed in either CMD or ENTRYPOINT
Examples
FROM al
-
Updated
Jan 24, 2022 - HTML
The example shown here (https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/data-sources/key_vault_secrets) has a for_each on the data source. I used it for one of my use cases, but it throws the below error.
data "azurerm_key_vault" "cpe_akv" {
name = "cpe"
resource_group_name = "cpe-secrets"
}
data "azurerm_key_vault_secrets" "secrets" {
key_vaul
- terrascan version: 1.9.0
- terraform version: 1.0.1
Enhancement Request
Other security scanning tools (e.g. checkov and tfsec) have a --soft-fail flag or equivalent option that allows you to always exit with 0 status.
Extremely useful when running the tool without halting a pipeline for example.
I currently use a workaround, but something more concrete would be very desira
-
Updated
Jan 8, 2022
-
Updated
Jan 24, 2022 - HCL
-
Updated
Jan 8, 2022 - Go
-
Updated
Jan 24, 2022 - Go
-
Updated
Dec 17, 2021 - Go
-
Updated
May 16, 2021
Created by Mitchell Hashimoto, HashiCorp
Released July 28, 2014
Latest release 5 days ago
- Repository
- hashicorp/terraform
- Website
- www.terraform.io
- Wikipedia
- Wikipedia

