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 10,340 public repositories matching this topic...
## Python/Regex fix
This is a reminder for me or a task if anyone wants :P
Basically, The last two questions aren't really regex's questions.
To do:
- Move said questions to correct place.
- Add new regex questions (Python related!)?
- Maybe add a new ## Regex section, as it is a valuable skill
-
Updated
Sep 17, 2021 - Go
Hi. I am using v0.28.18 terragrunt.
I want to apply tf module in two different AWS regions. And I want to keep state for each region in different s3 keys like:
terragrunt-test/terraform-us-east-1.tfstate
terragrunt-test/terraform-us-east-2.tfstate
The only way I thought I could do that was using locals. My configurations:
###### account1.tfvars:
aws_profile = "account1"
aws_region =
-
Updated
May 25, 2021
It does not look like we can detect "Fast snapshot restore" from the Terraform resource. Reading the AWS pricing page > "EBS Fast Snapshot Restore" example, I think we should hide that cost component by default and instead add a "fast_snapshot_restore_hours: 2 # Number
centos 8.x 支持计划
centos 8.2 已经发布了,想了解下对 centos 8.x 的支持计划大概是怎样的,谢谢。
-
Updated
Aug 5, 2021 - Shell
-
Updated
Sep 17, 2021 - Go
-
Updated
Sep 20, 2021 - Rust
Is your feature request related to a problem? Please describe.
Yes. We've inherited a terraform repo with a lot of legacy problems. We've introduced checkov to ensure new config going
forward meets our standards. We've also generated baseline files for all of the existing legacy terraform config, so that we only fail checks for new problems. However, we'd like to keep visibility on all
-
Updated
Sep 19, 2021 - HTML
Not sure if this is a feature request or a bug, but when using this resource against a windows vm that is using a secured custom version of the mssql server image, the resource will time out on the apply. The custom image we are using does work on the vm without using this resource, which makes me believe this an issue with the resource and not the image.
- 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
Sep 16, 2021
-
Updated
Sep 20, 2021 - HCL
-
Updated
May 16, 2021
-
Updated
Aug 31, 2021 - Go
Description
For the non-deep mode, which is the default driftctl scan
command, we display every time all the information about "unmanaged", "deleted", "drifted", "managed" resources, and the coverage.
It's quite unhelpful here to display the "drifted" resources since it would be ALL THE TIME equal to 0.
Example
Found 14 resource(s)
- 21% coverage
- 3 resource(s) managed
Created by Mitchell Hashimoto, HashiCorp
Released July 28, 2014
Latest release 5 days ago
- Repository
- hashicorp/terraform
- Website
- www.terraform.io
- Wikipedia
- Wikipedia