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.
In a directory that does not yet have a lock file, I am running terragrunt providers lock -platform=darwin_amd64 -platform=linux_amd64 and am noticing the error:
- Fetching hashicorp/aws 3.26.0 for darwin_amd64...
- Obtained hashicorp/aws checksums for darwin_amd64 (signed by HashiCorp)
- Fetching hashicorp/aws 3.26.0 for linux_amd64...
Error: Could not retrieve providers for lockin
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
centos 8.2 已经发布了，想了解下对 centos 8.x 的支持计划大概是怎样的，谢谢。
Describe the bug
GEN003 is triggering for the name of a secret in a github_actions_organization_secret resource. Going off the documentation for GEN003, it should only be triggering for secret VALUES, and not secret NAMES.
To Reproduce
variable "value"
Do not allow action “*” or resources “*” in an IOT Policy
Example policies are here: https://docs.aws.amazon.com/iot/latest/developerguide/example-iot-policies.html
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iot-policy.html
https://www.terraform.io/docs/providers/aws/r/iot_policy.html
Please explain the changes you made here and link to any relevant issues.
Not a big issue but when generating a plan on mac vs linux yamlencode generates different output. This function is still experimental and may change in the future, for a consistent output we could use jsonencode until yamlencode is ready.
linux:
It'd be good to have a consistent warning for the case where no provider constructs were generated in .gen
Example:
Created by Mitchell Hashimoto, HashiCorp
Released July 28, 2014
Latest release 6 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: