@stacksofplates said in Terratest:

I wrote a new article on unit testing Terraform modules with Terratest.

https://hooks.technology/2020/03/testing-terraform-with-terratest/

Nice article, I've never played with Teraform yet but its on my list.

Ok. I figured it out.

Using the output from above through trial and error this was my answer.

subnet_id = data.terraform_remote_state.network_configuration.outputs.mysubnet_name_id

In this example your subnet is named mysubnet_name

Azure Key Vault is great! It makes using secured credentials in Azure resources easy.

@Obsolesce said in Deploy Azure resources with Terraform:

@IRJ said in Deploy Azure resources with Terraform:

@Obsolesce said in Deploy Azure resources with Terraform:

@IRJ said in Deploy Azure resources with Terraform:

@Obsolesce

@IRJ said in Deploy Azure resources with Terraform:

@Obsolesce

Yeah good stuff. I have a couple Udemy courses on it.

Something I didn't see in this article was that Cloud Shell has Terraform built in... so you really don't even need to install it. I try to keep things serverless and source controlled, so I wouldn't want to install Terraform.

As long as it uses the latest version of terraform. There are many differences between current and last release.

Screenshot_20190805-163610_Edge.jpg

Cool. Yeah 11 vs 12 are much different. Alot of things have to be redone

A good workflow would be using Packer to build your immutable images with Ansible. That way you don't need to log into the image, just make a new image with your changes using the same process, and then deploy those images with Terraform.

You can do some CM in terraform also. You can do remote exec after it finishes like this:

provisioner "file" { source = "file.config" destination = "/etc/configs/file.confg" }

'You can ouput info for Ansible (or others) from Terraform after it finishes. For example:

provisioner "local-exec" { command = "echo ${aws_instance.example.public_dns} >> inventory" } ouput "name" { value = "${aws_instance.example.public_dns}" }