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.
Requesting that you add the new Gitlab Provider as a new VCS Provider.
See here for the provider details: https://registry.terraform.io/providers/gitlabhq/gitlab/latest
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 =
Add package manager support for windoz users with chocolatey:
like here: https://github.com/bridgecrewio/yor-choco
centos 8.2 已经发布了，想了解下对 centos 8.x 的支持计划大概是怎样的，谢谢。
Currently the cdktf watch command only supports reading the projects root .gitignore file to check which files to ignore when watching files for synth.
It should also support nested .gitignore files.
E.g. this utility could be extended:
https://github.com/hashicorp/terraform-cdk/blob/962ffa75e726d0506e72fe559e2c50331aba9180/packages/cdktf-cli/lib/server/util.ts#L10-L13
For simple modules the generated documentation contains a lot of sections that simply say "no outputs", "no resources", etc.
Of course it is possible to hide these "empty" sections manually, but if the module changes in the future, you have to explicitly remove it again.
It would be great if terraform-do
Resolves #774
The change is intended to improve the ability to manage worker groups using maps. Which should allow to more flexibly add/remove worker groups (improve this: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/docs/faq.md#how-do-i-safely-remove-old-worker-groups).
The change includes suggested in #774 changes which include:
Description
To complete #554, it can make sense to add resource source details for missing resources
Example
Follow pull-request attached to issues #874 #875 #876 for examples of implementation
Created by Mitchell Hashimoto, HashiCorp
Released July 28, 2014
Latest release 14 days ago
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: