Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Does Terraform provide a mechanism to find the provider version?

S
Saumya last edited by

Other than reading .terraform.lock.hcl is there a mechanisms in Terraform to find the version of the providers I am using with the cli interface?

I don't see the version when I run terraform providers or the ability to add a -v flag (or another flag) under terraform providers --help
Reply Quote 0
1 Reply Last reply
Mystic last edited by
You can find the version of your providers with terraform version
```
❯ terraform version
Terraform v1.1.9
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v3.75.1
```
With https://github.com/stedolan/jq
```
❯ terraform version -json | jq .provider_selections
{
  "registry.terraform.io/hashicorp/aws": "3.75.1"
}
```
terraform version -json | jq .provider_selections

I opened a https://github.com/hashicorp/terraform/issues/31048#issue-1236104011
Reply Quote 0
1 Reply Last reply

2
Posts

0
Views

Suggested Topics

Find relevant domain/hosted zone under which to host subdomain
Continuous Integration and Delivery (CI, CD) • dns amazon web services terraform • • inna

2

0
Votes

2
Posts

1
Views

R

Short answer: I don't believe that is possible. In my opinion, I suspect this problem has more to do with process and responsibilities than it does with Terraform. You said: It's possibly that I could go with the fist approach (e.g. where example.com is my only hosted zone) only for someone to later add a hosted zone for the mysite subdomain. If that occurred I wouldn't want to have to change my code... Terraform is best when at least most of its associated resources are Terraform-managed. That means you should be managing your zones, too, not just your records. Which begs the question: why isn't your zone in Terraform? If your zone was Terraform-managed, the impact of that change should be evident in a terraform plan to anyone who might come along to change it. Even if it references a zone in a different remote state file, a tool like runatlantis.io could show that diff in the Github PR before merging. Let's say this is the worst-case scenario: you managed the records, it's a different team that creates and manages the zones, and they don't want to use Terraform. In that case, perhaps your DNS records shouldn't be in Terraform, either. Terraform is arguably too stateful for that. Perhaps a few python boto3 scripts can do everything you need it to.
E

Terraform | After upgrading to 0.12 receive a lots of error "unsupported value for "%s" at 0: string required."
Continuous Integration and Delivery (CI, CD) • terraform • • emerson

2

0
Votes

2
Posts

1
Views

There is a clue in your error message, but it's only helpful if you know what you're looking for: | module.mongodb.instance_names is tuple with 1 element | module.mongodb.private_ip is list of string with 1 element Your declaration of the instance_names output includes this expression: ["${data.template_file.instance_tags_name.*.rendered}"] The data.template_file.instance_tags_name.*.rendered part of this returns a list of strings, and then the [ ... ] around it then wraps an extra list (or rather, tuple) around it, creating a single-element tuple containing a list of strings. That's why the tuple contains only one element, rather than having an element for each of your count instances. This situation is what the upgrade guide discusses under Referring to List Variables, and that documentation includes some more background information on why this previously worked in 0.11 and why the change is required now. To fix this, you should refer to just the splat expression alone, producing the flat list of strings that your formatlist call is expecting: output "instance_names" { value = data.template_file.instance_tags_name.*.rendered } The automatic configuration upgrade tool described in the upgrade guide can make this change automatically in some cases, so I'd recommend using that as a starting point for your 0.12 upgrade process. It isn't able to fix everything, but it will do a lot of the straightforward rewriting work for you and will emit warnings about some more complex situations it's unable to handle.
Terraform workspaces vs isolated directories?
Continuous Integration and Delivery (CI, CD) • deployment terraform terraform workspace • • Mystic

2

0
Votes

2
Posts

0
Views

F

Workspaces are an unnecessary complexity which causes the possibility that you destroy your prod environment (or leak secrets). It is a much better practice to switch backends, and that is noted in the docs: https://www.terraform.io/language/state/workspaces In particular, organizations commonly want to create a strong separation between multiple deployments of the same infrastructure serving different development stages (e.g. staging vs. production) or different internal teams. In this case, the backend used for each deployment often belongs to that deployment, with different credentials and access controls. Named workspaces are not a suitable isolation mechanism for this scenario. Instead, use one or more re-usable modules to represent the common elements, and then represent each instance as a separate configuration that instantiates those common elements in the context of a different backend. In that case, the root module of each configuration will consist only of a backend configuration and a small number of module blocks whose arguments describe any small differences between the deployments. The new hotness is a backend file, which you can choose at init: https://www.terraform.io/language/settings/backends/configuration#file
K

How to use kubernetes_service data provider in Terraform?
Continuous Integration and Delivery (CI, CD) • terraform terraform module • • Kadyn

2

0
Votes

2
Posts

1
Views

The provider documentation you quoted here seems to have a mistake. It talks about using the two providers together in the same module but it seems like it really means in the same configuration. The problem arises because Terraform needs to configure a provider in order to plan with it, and so everything inside a provider "kubernetes" block must be known at the time of planning. This means you can't use anything in there which isn't created yet. That documentation is trying to tell you that you'll need to split the configuration that declares your Kubernetes cluster from all of your configurations that configure or make use of the Kubernetes cluster, and then you can terraform apply the creation of the cluster first, and then separately terraform apply your other configurations that interact with it using the kubernetes provider.
T

Resources don't seem to show up in Terraform state after import
Continuous Integration and Delivery (CI, CD) • amazon web services terraform • • terrea

2

0
Votes

2
Posts

1
Views

I figured it out. The stub resource has to have a provider that is configured with the proper AWS region. All these security groups were in us-west-2. You need this: resource "aws_security_group" "rds-launch-wizard-2" { provider = aws.us_west_2 } instead of this: resource "aws_security_group" "rds-launch-wizard-2" {} This assumes you have a provider already configured thus: provider "aws" { region = "us-west-2" alias = "us_west_2" }
G

Is there a way to lint Terraform?
Continuous Integration and Delivery (CI, CD) • terraform linting • • guilherme

2

0
Votes

2
Posts

1
Views

Z

terraform fmt The terraform fmt command is used to rewrite Terraform configuration files to a canonical format and style.
Terraform aws_ecr_repository resource always attempts to destroy
Continuous Integration and Delivery (CI, CD) • amazon web services terraform amazon ecs • • Bogopo

2

0
Votes

2
Posts

1
Views

N

In your terraform {...} section you need a backend directive to store your state somewhere: https://www.terraform.io/docs/state/remote.html (OP later explain that the code above is just a module imported from a main file). S3 backends might be the easiest to use and probably to most commonly used backends to store remote state across different executions of Terraform: terraform { backend "s3" { bucket = "mybucket" key = "path/to/my/key" region = "us-east-1" } } Please note that Terraform init will not import existing resources into a state (there's Terraform import for that). It will therefore try to create new ones and you will get a conflict on the name. The Terraform documentation gives some pointers on how to use Terraform in automation and that includes using remote state. It is possible to prevent the creation of the ECR through a data block as you hinted (with count = ...), but doing so would feel like a hack to me. Once you have your remote backend configured, you can double check that everything works as expected by using the terraform state command in your pipeline. I would suggest using the show subcommand on a resource you expect to be there in order to validate that the state indeed contains the resource: terraform init -input=false terraform state show module.name-of-your-module.aws_ecr_repository.frontend_ecr_repo_creation
E

Terraform | Error "transport is closing" when "terraform apply" after upgrading to 0.12
Continuous Integration and Delivery (CI, CD) • terraform • • esther

2

0
Votes

2
Posts

1
Views

M

It's a bug in terraform aws ec2 module, last working version is 2.5.0
R

Terraform get subnet id by it's CIDR block
Continuous Integration and Delivery (CI, CD) • amazon web services terraform aws vpc terraform module aws subnets • • Raziyah00

2

0
Votes

2
Posts

0
Views

J

It seems that you already know which CIDR ranges you wish to look up, and that you are trying to find the corresponding subnet id for each of them. You can achieve that by using the aws_subnet data source with https://www.terraform.io/language/meta-arguments/for_each , to tell Terraform to make a separate call to that data source for each of your CIDR ranges. I'm assuming that the my_subnets example in your question is inside a locals block and so it has declared and defined local.my_subnets to hold that list of strings. data "aws_subnet" "example" { for_each = toset(local.my_subnets) cidr_block = each.key } A resource with for_each set appears in expressions as a map of objects where the map keys are the same as the for_each map keys (or, in this case, set elements). Therefore you can derive from this a mapping from CIDR block to subnet ID: locals { subnet_ids = tomap({ for cidr, subnet in data.aws_subnet.example : cidr => subnet.id }) } or, if you don't actually care about the correspondence between the CIDR blocks and the ids and just want a flat set of ids, you can just ignore the instance keys: locals { subnet_ids = toset([ for subnet in data.aws_subnet.example : subnet.id ]) } The second of these seems to be what is expected by the subnet_ids argument you want to assign to: vpc_options { subnet_ids = [ for subnet in data.aws_subnet.example : subnet.id ] } (I omitted the toset call when inlining this expression in the argument, because the schema for that vpc_options block will already tell Terraform whether subnet_ids is a set or a list, and so Terraform can convert automatically in that case.)
Terraform - aws_security_group_rule doesn't support import
Continuous Integration and Delivery (CI, CD) • amazon web services terraform • • Alberto

2

0
Votes

2
Posts

1
Views

D

Did you try to import in flat setup than modular setup? It seems that in modular setup there is a bug with Terraform. https://github.com/terraform-providers/terraform-provider-aws/issues/559
Error when creating new recource using backend AWS s3
Continuous Integration and Delivery (CI, CD) • terraform amazon s3 • • emmalee

2

0
Votes

2
Posts

1
Views

Guys I discovered what happened. It was necessary to apply these two resources that I informed (project_data and environment_data), but they were in the above directories and I was not aware. Something like this: Application | |-Environment |-environment_data.tf | |- project_data.tf
M

How to find future (planned) versions of Docker?
Continuous Integration and Delivery (CI, CD) • docker • • magpie

2

0
Votes

2
Posts

1
Views

I'll assume you're talking about Docker Engine for Linux. Docker doesn't plan releases like that currently. What they do is: Release major and minor versions on GitHub: https://github.com/moby/moby/releases Put release notes in their docs: https://docs.docker.com/engine/release-notes The version number is date based on the month they begin the release process, so the current version "20.10" started its release process in October, 2020 and was eventually released in December, 2020. The last major release before that was 19.03. Finally, you can see what they are working on (features) and what's next on their Roadmap https://github.com/docker/roadmap/projects/1
terraform chef provisioning - cannot validate certificate for 10.90.239.223 because it doesn't contain any IP SANs
Continuous Integration and Delivery (CI, CD) • security ssl terraform chef • • Bogopo

2

0
Votes

2
Posts

1
Views

D

Answered on Slack, the likely first issue here is that the output from openssl req is not a cert, it's a CSR. But there are some other lingering issues here too. It is recommended to use something like Certstrap to do internal cert generation rather than raw openssl commands as the modern standards are quite fiddly.
O

Using counted data source in non-counted provider block in Terraform
Continuous Integration and Delivery (CI, CD) • terraform terraform module google kubernetes engine • • Oba22

2

0
Votes

2
Posts

1
Views

D

If I have read this correctly you are trying to target different clusters with your provider so you can then use a helm_release. You need to have distinct providers for each cluster and differentiate them with an alias so. provider "helm" { kubernetes { host = "https://my_endpoint1" token = "provider.access_token1" cluster_ca_certificate = "base64encodedcerthere1" } } provider "helm" { alias = "cluster2" kubernetes { host = "https://my_endpoint2" token = "provider.access_token2" cluster_ca_certificate = "base64encodedcerthere2" } } the first provider will be used where no alias is provided and the second used only where an alias is used for the provider so for example: resource "helm_release" "example" { name = "my-bob-release" ... } the above uses the default un-named provider resource "helm_release" "example" { provider = helm.cluster2 name = "my-bob-release" ... }
Deploying different versions of the same application stack in the same system
Continuous Integration and Delivery (CI, CD) • docker deployment • • Laycee

2

0
Votes

2
Posts

1
Views

P

First of all, I would not recommend to use a single system for running stable and testing version both on the same system. There are many reasons for this such as: Your testing version can cause cpu and memory spikes on system which will ultimately affect your stable version and end users. Secondly, it will be difficult to manage the dependencies and resources for multiple versions in a single system. It can also take a lot of debugging time if the monitoring is not properly setup. Ideally, you should use 2 different system. One for running the stable version and other testing versions. It will be easy to manage and always a good practice to keep it on different stack. Still, if you want to use a single system, then yes, you can use docker which will avoid a lot of conflict issues which can arise. Also, the dependencies and shared libraries can be managed easily with different docker images and running docker containers. If the team is proficient in docker, you can also use docker swarm to setup clusters. You can setup different clusters for stable and testing versions. I hope you chose the best possible option and implement it.

Does Terraform provide a mechanism to find the provider version?

With https://github.com/stedolan/jq

Suggested Topics

Find relevant domain/hosted zone under which to host subdomain Continuous Integration and Delivery (CI, CD) • dns amazon web services terraform • • inna

Terraform | After upgrading to 0.12 receive a lots of error "unsupported value for "%s" at 0: string required." Continuous Integration and Delivery (CI, CD) • terraform • • emerson

Terraform workspaces vs isolated directories? Continuous Integration and Delivery (CI, CD) • deployment terraform terraform workspace • • Mystic

How to use kubernetes_service data provider in Terraform? Continuous Integration and Delivery (CI, CD) • terraform terraform module • • Kadyn

Resources don't seem to show up in Terraform state after import Continuous Integration and Delivery (CI, CD) • amazon web services terraform • • terrea

Is there a way to lint Terraform? Continuous Integration and Delivery (CI, CD) • terraform linting • • guilherme

Terraform aws_ecr_repository resource always attempts to destroy Continuous Integration and Delivery (CI, CD) • amazon web services terraform amazon ecs • • Bogopo

Terraform | Error "transport is closing" when "terraform apply" after upgrading to 0.12 Continuous Integration and Delivery (CI, CD) • terraform • • esther

Terraform get subnet id by it's CIDR block Continuous Integration and Delivery (CI, CD) • amazon web services terraform aws vpc terraform module aws subnets • • Raziyah00

Terraform - aws_security_group_rule doesn't support import Continuous Integration and Delivery (CI, CD) • amazon web services terraform • • Alberto

Error when creating new recource using backend AWS s3 Continuous Integration and Delivery (CI, CD) • terraform amazon s3 • • emmalee

How to find future (planned) versions of Docker? Continuous Integration and Delivery (CI, CD) • docker • • magpie

terraform chef provisioning - cannot validate certificate for 10.90.239.223 because it doesn't contain any IP SANs Continuous Integration and Delivery (CI, CD) • security ssl terraform chef • • Bogopo

Using counted data source in non-counted provider block in Terraform Continuous Integration and Delivery (CI, CD) • terraform terraform module google kubernetes engine • • Oba22

Deploying different versions of the same application stack in the same system Continuous Integration and Delivery (CI, CD) • docker deployment • • Laycee

Find relevant domain/hosted zone under which to host subdomain
Continuous Integration and Delivery (CI, CD) • dns amazon web services terraform • • inna

Terraform | After upgrading to 0.12 receive a lots of error "unsupported value for "%s" at 0: string required."
Continuous Integration and Delivery (CI, CD) • terraform • • emerson

Terraform workspaces vs isolated directories?
Continuous Integration and Delivery (CI, CD) • deployment terraform terraform workspace • • Mystic

How to use kubernetes_service data provider in Terraform?
Continuous Integration and Delivery (CI, CD) • terraform terraform module • • Kadyn

Resources don't seem to show up in Terraform state after import
Continuous Integration and Delivery (CI, CD) • amazon web services terraform • • terrea

Is there a way to lint Terraform?
Continuous Integration and Delivery (CI, CD) • terraform linting • • guilherme

Terraform aws_ecr_repository resource always attempts to destroy
Continuous Integration and Delivery (CI, CD) • amazon web services terraform amazon ecs • • Bogopo

Terraform | Error "transport is closing" when "terraform apply" after upgrading to 0.12
Continuous Integration and Delivery (CI, CD) • terraform • • esther

Terraform get subnet id by it's CIDR block
Continuous Integration and Delivery (CI, CD) • amazon web services terraform aws vpc terraform module aws subnets • • Raziyah00

Terraform - aws_security_group_rule doesn't support import
Continuous Integration and Delivery (CI, CD) • amazon web services terraform • • Alberto

Error when creating new recource using backend AWS s3
Continuous Integration and Delivery (CI, CD) • terraform amazon s3 • • emmalee

How to find future (planned) versions of Docker?
Continuous Integration and Delivery (CI, CD) • docker • • magpie

terraform chef provisioning - cannot validate certificate for 10.90.239.223 because it doesn't contain any IP SANs
Continuous Integration and Delivery (CI, CD) • security ssl terraform chef • • Bogopo

Using counted data source in non-counted provider block in Terraform
Continuous Integration and Delivery (CI, CD) • terraform terraform module google kubernetes engine • • Oba22

Deploying different versions of the same application stack in the same system
Continuous Integration and Delivery (CI, CD) • docker deployment • • Laycee