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).

Variable for Terraform Workspace name?

chanisef

When I run terraform apply in a new workspace, I get

openstack_networking_port_secgroup_associate_v2.network_project_k3s: Creation complete after 1s [id=4543b73b-541e-40c3-a311-5b1f553b9d58]
╷
│ Error: Error trying to get network information from the Network API: More than one network found for name net_project
│ 
│   with openstack_compute_instance_v2.test-server,
│   on main.tf line 137, in resource "openstack_compute_instance_v2" "test-server":
│  137: resource "openstack_compute_instance_v2" "test-server" {

I suppose I'm getting this because OpenStack's network names are globally unique. How can I incorporate the workspace name in the network name?

resource "openstack_networking_network_v2" "net_project" {
  name           = "net_project_${WORKSPACE}"
  admin_state_up = "true"
}

K
Kadir last edited by
The variable I ended up using was
```
${terraform.workspace}
```
You can find more information about it under "Current Workspace Interpolation"
- https://www.terraform.io/language/state/workspaces#current-workspace-interpolation
Reply Quote 0
1 Reply Last reply

2
Posts

0
Views

Suggested Topics

S

TerraForm separate stages
Continuous Integration and Delivery (CI, CD) • terraform terraform module terraform workspace • • Saumya

2

0
Votes

2
Posts

0
Views

J

I don't think there are any best practices because it would depend on both your company structure as well as how your developers manage their code in SCM (gitflow, trunk, etc). Lets start with the statements that seem to be in contradiction. I think quoted like that they do seem to tell a different story. But lets look at the start of the paragraph where the first quote came from. When Terraform is used to manage larger systems, teams should use multiple separate Terraform configurations that correspond with suitable architectural boundaries within the system so that different components can be managed separately and, if appropriate, by distinct teams. So it's saying that when you have multiple teams using the same terraform directory (aka configuration) then... Workspaces alone are not a suitable tool for system decomposition, because each subsystem should have its own separate configuration and backend, and will thus have its own distinct set of workspaces. Which makes sense. Each team will need different things from their workspace and since all the teams will be sharing workspaces then it kinda falls apart. So in conclusion, different directories and workspaces can be used to separate environments in Terraform but they have certain limitations. In the tutorial you linked, I think it's explained even better: To separate environments with potential configuration differences, use a directory structure. Use workspaces for environments that do not greatly deviate from one another, to avoid duplicating your configurations. The second part of your question about recommendations can get somewhat complicated depending on what level of CICD and automation your company currently has. If your infra is small and the number of changes every month is pretty minimal then it's probably fine to just checkout the code, make the change and deploy it locally. But if you are a large organization with 100's of changes a week, then you are probably going to want to automate the deployments. A common way of doing that is to trigger CICD on new PR's or changes to certain branches. From there you can have your CICD engine change workspaces based on the branch name. Or more commonly for older companies who used Terraform before workspaces existed, you can just set the state path to something like ${env}/tf.state because that really has the same effect as just using workspaces. I'm a Terraform and https://github.com/gruntwork-io/terratest/releases/tag/v0.28.5 contribtutor. I'm also the author of https://github.com/DontShaveTheYak/cf2tf and the https://github.com/DontShaveTheYak/terraform-module-template .
D

Terraform Dynamic Block with list intro them
Continuous Integration and Delivery (CI, CD) • amazon web services terraform terraform module • • derk

2

0
Votes

2
Posts

1
Views

P

I'm resolved my question like bellow: I discovered that some arguments that I used before not was used when you use the s3_origin and them are used with custom_orogin Was necessary used too variables type=list(object({foo=bar}) for my dynamic blocks lists. Part of my module bellow: main.tf dynamic "origin" { for_each = var.origin content { domain_name = origin.value.domain_name origin_id = origin.value.origin_id s3_origin_config { origin_access_identity = origin.value.origin_access_identity } } } vars.tf variable "origin" { type = list(object({ domain_name = any, origin_id = string, origin_access_identity = string })) description = "One or more origins for this distribution (multiples allowed)." } Another thing that I learned it's when you set a default=value onto variable type same this var is (optional) you turn them (required).
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.
Cross Account EC2 Access from within Amazon Workspace
Continuous Integration and Delivery (CI, CD) • amazon web services amazon ec2 aws cli • • Mystic

2

0
Votes

2
Posts

1
Views

D

Use a VPC peering between the two accounts so that your instance from account A will be able to communicate with account B. This will work if you have different subnet CIDR blocks in the two accounts. If you have the same (i.e. in both VPC, your subnets are in 192.168.0.0/16), then change the one that has the least impact and proceed with a VPC peering. Finally, you will have to configure your security group to allow the bastion to communicate with the other instance. Here are more details for AWS VPC peering: VPC peering
J

dev/stage/prod in separate AWS accounts, managed via terraform cloud workspaces, how can I use lb ip in DNS records for each env?
Continuous Integration and Delivery (CI, CD) • dns amazon web services terraform terraform workspace • • Jolied

2

0
Votes

2
Posts

0
Views

D

One simple way would be to delegate the subdomain of mydomain.com for each account to that account's Route53 service. After you do this, the credentials that allow Terraform to create load balancers, servers, and other things in the Dev account can also create/update/delete the DNS records for dev.mydomain.com. The different credentials that manage resources in the Stage account can also manage DNS entries in stage.mydomain.com. The DNS for the different accounts is kept separate just like the other resources. The way to do this is to create dev.mydomain.com as a public domain in the Dev account's Route53. Take down the list of DNS servers reported there, and add them as NS records for the name dev.mydomain.com in the Root account's Route53. Follow a similar pattern for the subdomains for the other accounts.
Z

Create dynamic resources using 'for_each' or 'for'
Continuous Integration and Delivery (CI, CD) • terraform • • zymir

2

0
Votes

2
Posts

1
Views

Y

you need to use count, and with it you should be able to access item by index: https://www.terraform.io/docs/configuration/resources.html#the-count-object
J

How to use terraform import with module
Continuous Integration and Delivery (CI, CD) • terraform • • juvenalb

2

0
Votes

2
Posts

1
Views

The terraform import command uses the "Resource Address" syntax, which is a way to talk about objects in a configuration from outside of that configuration. (This is as opposed to references in the main Terraform language, which are always resolved in the context of a particular module.) To refer to a resource that is declared in a child module, you can add a module path to the beginning of the address: terraform import module.assets.aws_s3_bucket.machine-learning BUCKET-NAME
Terraform: Sanitize a map that may be a map of strings or map of maps or combo of both
Continuous Integration and Delivery (CI, CD) • terraform • • morde

2

0
Votes

2
Posts

1
Views

K

Following the documentation a map is a collection of key/values with a constraint: "...accepts any element type as long as every element is the same type" source So the input map you have declared, is already an invalid map for Terraform 0.12 (at least) Below the example of the error produced: variable "cidrs" { description = "" type = map default = [ ["1.1.1.1"], ["2.2.2.2", "3.3.3.3"], { C = ["4.4.4.4"] D = ["5.5.5.5"] }] } When validating an error is raised: $> terraform validate Error: Invalid default value for variable on vars.tf line 65, in variable "cidrs": 65: default = [ 66: ["1.1.1.1"], 67: ["2.2.2.2", "3.3.3.3"], 68: { 69: C = ["4.4.4.4"] 70: D = ["5.5.5.5"] 71: }] This default value is not compatible with the variable's type constraint: map of any single type required. Been that said, if we can generalize A and B as "values which are lists" and Group1 as "values which are maps" and the input is a fixed type ordered we can use a tuple or an object, this can be solve in a more readable (and maintainable) way. If so, let us know so we can extend this answer.
O

What is an example of an error that tflint will catch that `terraform init` will not error on?
Continuous Integration and Delivery (CI, CD) • terraform • • Oba22

2

0
Votes

2
Posts

0
Views

A

These are the default https://github.com/terraform-linters/tflint-ruleset-terraform/blob/main/docs/rules/README.md for tflint. Most of these rules will have an example of how to trigger it and remediate it. A simple one you could use is the terraform_comment_syntax https://github.com/terraform-linters/tflint-ruleset-terraform/blob/main/docs/rules/terraform_comment_syntax.md . You can trigger it by using a // comment inside a *.tf file.
J

How do I run Terraform with AWS MFA?
Continuous Integration and Delivery (CI, CD) • authentication amazon web services terraform • • Jolied

2

0
Votes

2
Posts

1
Views

Z

The solution is to specify an assume_role statement: provider "aws" { profile = "default" assume_role { role_arn = "arn:aws:iam::[ACCOUNT_ID]:role/terraform-test-role" } }
O

Why is Terraform not picking up locals.tf?
Continuous Integration and Delivery (CI, CD) • terraform • • Oba22

2

0
Votes

2
Posts

0
Views

S

Because you made it a variable! This one confused me for a minute too. Your locals are defined correctly. You reference it correctly. So why is terraform prompting for it? Just because you define it as a variable. Since you're not using var.certificate_arn anywhere, defining it is a variable is not needed. But since you did define it as a variable, terraform is going to diligently ask for it. Getting rid of the variable definition should fix your issue. If later you want to turn it into a variable, fine. But you'll need to get rid of the local and reference var. instead of local..
G

Sub-subdomain Domain name for different environment
Continuous Integration and Delivery (CI, CD) • dns • • gionna

2

0
Votes

2
Posts

1
Views

K

Both are completely correct. It can differ organisation by organisation. Also, once you start using one of the domain namespace type, you will gradually remember the format and no issues will come. However, I can see one issue here which is related to SSL. If you go with any one of the above mentioned namespaces, you need to generate multiple SSL certificates such as *.api.superproduct.com and *.front-end.superproduct.com. If you go with other namespace type then SSL certs will be required for *.staging.superproduct.com, *.qa.superproduct.com and *.development.superproduct.com. To avoid this, I would suggest you to have the domains in either of the following formats. <component-name>-<env-name>.superproduct.com</code></li> </ol> <p>Examples are: <code>api-qa.superproduct.com</code>, <code>api-staging.superproduct.com</code> etc.</p> <ol start="2"> <li> -.superproduct.com Examples are: qa-api.superproduct.com, staging-api.superproduct.com etc. In this case, only one SSL certificate for *.superproduct.com will be required. You can go ahead with the best possible option as per your requirements and analysis.
Unable to authenticate with Terraform AWS provider
Continuous Integration and Delivery (CI, CD) • amazon web services terraform • • Marcee

2

0
Votes

2
Posts

0
Views

E

If you have multiple profiles in your credentials file, you need to state which profile you want to use, otherwise it will use [default]: credentials file: [default] aws_access_key_id = xxxxxxxx aws_secret_access_key = xxxxxxxx [profile2] aws_access_key_id = yyyyyyyy aws_secret_access_key = yyyyyyyyy terraform code: provider "aws" { region = var.aws_region shared_credentials_file = "/Users/samueldare/.aws/credentials" profile = "profile2" } As stated in the https://registry.terraform.io/providers/hashicorp/aws/latest/docs#shared-configuration-and-credentials-files
How to get VPC id in Terraform module?
Continuous Integration and Delivery (CI, CD) • terraform aws vpc • • briley

2

0
Votes

2
Posts

1
Views

Without seeing the contents of your two modules I'm guessing a bit, but it looks like you have an AWS VPC declared in your vpc module and some subnets declared in your prod_subnets module and you are asking how the configuration of the subnets can get access to the VPC ID. If so, the answer is that the vpc module must export the VPC ID as an output value and then the prod_subnets module must accept the VPC ID as an input variable. In your vpc module, you can declare a vpc_id output value like this, for example in a file modules/vpc/outputs.tf: output "vpc_id" { value = aws_vpc.production_vpc } In your prod_subnets module you can declare a vpc_id input variable, for example in a file modules/vpc/modules/subnets/production/outputs.tf: variable "vpc_id" { type = string } Then in your existing modules/vpc/modules/subnets/production/production.tf file, on line 162, change the vpc_id argument for the subnet to refer to that variable: vpc_id = var.vpc_id Finally, you must then edit the top-level file whose source code you shared in your question to pass the value between the two modules, like this: module "vpc" { source = "./modules/vpc" } module "prod_subnets" { source = "./modules/vpc/modules/subnets/production" vpc_id = module.vpc.vpc_id } module.vpc.vpc_id means to take the value of the vpc_id output value from the vpc module.
Z

How to create databases, users and grants with terraform mysql and output the created credentials?
Continuous Integration and Delivery (CI, CD) • terraform • • zymir

2

0
Votes

2
Posts

1
Views

C

To ensure separation and use in other environments, make sure to have an outputs file and set each password as an output. TF Output Docs. I haven't done much with for each as it was just released last time I used terraform. I would imagine a way to iterate over passwords and assign them as outputs. once you have the output set for the module, I would then have my consuming terraform put those values in a password vault of some kind. You can use Azure's Key Vault. TF Azure Key Vault, or any other solution. Just ensure that the ops team has access to the destination. This way there isn't anything introduced between when/where the keys are generated and them being stored, reducing the chance for human error.

Variable for Terraform Workspace name?

Suggested Topics

TerraForm separate stages Continuous Integration and Delivery (CI, CD) • terraform terraform module terraform workspace • • Saumya

Terraform Dynamic Block with list intro them Continuous Integration and Delivery (CI, CD) • amazon web services terraform terraform module • • derk

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

Cross Account EC2 Access from within Amazon Workspace Continuous Integration and Delivery (CI, CD) • amazon web services amazon ec2 aws cli • • Mystic

dev/stage/prod in separate AWS accounts, managed via terraform cloud workspaces, how can I use lb ip in DNS records for each env? Continuous Integration and Delivery (CI, CD) • dns amazon web services terraform terraform workspace • • Jolied

Create dynamic resources using 'for_each' or 'for' Continuous Integration and Delivery (CI, CD) • terraform • • zymir

How to use terraform import with module Continuous Integration and Delivery (CI, CD) • terraform • • juvenalb

Terraform: Sanitize a map that may be a map of strings or map of maps or combo of both Continuous Integration and Delivery (CI, CD) • terraform • • morde

What is an example of an error that tflint will catch that `terraform init` will not error on? Continuous Integration and Delivery (CI, CD) • terraform • • Oba22

How do I run Terraform with AWS MFA? Continuous Integration and Delivery (CI, CD) • authentication amazon web services terraform • • Jolied

Why is Terraform not picking up locals.tf? Continuous Integration and Delivery (CI, CD) • terraform • • Oba22

Sub-subdomain Domain name for different environment Continuous Integration and Delivery (CI, CD) • dns • • gionna

Unable to authenticate with Terraform AWS provider Continuous Integration and Delivery (CI, CD) • amazon web services terraform • • Marcee

How to get VPC id in Terraform module? Continuous Integration and Delivery (CI, CD) • terraform aws vpc • • briley

How to create databases, users and grants with terraform mysql and output the created credentials? Continuous Integration and Delivery (CI, CD) • terraform • • zymir

TerraForm separate stages
Continuous Integration and Delivery (CI, CD) • terraform terraform module terraform workspace • • Saumya

Terraform Dynamic Block with list intro them
Continuous Integration and Delivery (CI, CD) • amazon web services terraform terraform module • • derk

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

Cross Account EC2 Access from within Amazon Workspace
Continuous Integration and Delivery (CI, CD) • amazon web services amazon ec2 aws cli • • Mystic

dev/stage/prod in separate AWS accounts, managed via terraform cloud workspaces, how can I use lb ip in DNS records for each env?
Continuous Integration and Delivery (CI, CD) • dns amazon web services terraform terraform workspace • • Jolied

Create dynamic resources using 'for_each' or 'for'
Continuous Integration and Delivery (CI, CD) • terraform • • zymir

How to use terraform import with module
Continuous Integration and Delivery (CI, CD) • terraform • • juvenalb

Terraform: Sanitize a map that may be a map of strings or map of maps or combo of both
Continuous Integration and Delivery (CI, CD) • terraform • • morde

What is an example of an error that tflint will catch that `terraform init` will not error on?
Continuous Integration and Delivery (CI, CD) • terraform • • Oba22

How do I run Terraform with AWS MFA?
Continuous Integration and Delivery (CI, CD) • authentication amazon web services terraform • • Jolied

Why is Terraform not picking up locals.tf?
Continuous Integration and Delivery (CI, CD) • terraform • • Oba22

Sub-subdomain Domain name for different environment
Continuous Integration and Delivery (CI, CD) • dns • • gionna

Unable to authenticate with Terraform AWS provider
Continuous Integration and Delivery (CI, CD) • amazon web services terraform • • Marcee

How to get VPC id in Terraform module?
Continuous Integration and Delivery (CI, CD) • terraform aws vpc • • briley

How to create databases, users and grants with terraform mysql and output the created credentials?
Continuous Integration and Delivery (CI, CD) • terraform • • zymir