A Terraform provisioner must be nested inside a resource configuration block.
A Terraform provisioner must be nested inside a resource configuration block.
In Terraform, provisioners are integral to the configuration of resources. They are used to execute scripts on a local or remote machine during the creation or destruction of resources. Provisioners can only be defined within the context of a resource block since their execution context is closely tied to the resource lifecycle. Therefore, a provisioner must be nested inside a resource configuration block to ensure proper execution and dependency management.
A: True. Example: resource "aws_instance" "web" { # ... provisioner "local-exec" { command = "echo The server's IP address is ${self.private_ip}" } }
To use a provisioner in Terraform, you must include it as part of a resource configuration block. This is because a provisioner operates on a resource that has been created or updated by Terraform.
I think ans is A
While it's common to place provisioners inside the resource block for clarity and organization, they can also be defined outside of the block at the same level. Both approaches are valid, and the choice depends on your preference and the organization of your Terraform code. The main point is that provisioners are associated with a specific resource and are configured within the resource block or at the same level in the code.
the question is stated provisioner must be. the key word being Must. They do not have to be so I voted B
https://developer.hashicorp.com/terraform/language/resources/provisioners/syntax Provisioners are used to execute scripts on a local or remote machine as part of resource creation or destruction. Provisioners can be used to bootstrap a resource, cleanup before destroy, run configuration management, etc. How to use Provisioners Note: Provisioners should only be used as a last resort. For most common situations there are better alternatives. For more information, see the sections above. If you are certain that provisioners are the best way to solve your problem after considering the advice in the sections above, you can add a provisioner block inside the resource block of a compute instance. resource "aws_instance" "web" { # ... provisioner "local-exec" { command = "echo The server's IP address is ${self.private_ip}" } }
A: true. for instance, resource "aws_instance" "testInstance" { ami = "${var.instance_ami}" instance_type = "${var.instance_type}" subnet_id = "${aws_subnet.subnet_public.id}" vpc_security_group_ids = ["${aws_security_group.sg_22.id}"] key_name = "${aws_key_pair.ec2key.key_name}" tags { "Environment" = "${var.environment_tag}" } provisioner "local-exec" { command = "echo ${aws_instance.testInstance.public_ip} >> public_ip.txt" } }
Examples given in "https://developer.hashicorp.com/terraform/language/resources/provisioners/connection" are not inside a resource configuration block. provisioner "file" { source = "conf/myapp.conf" destination = "/etc/myapp.conf" connection { type = "ssh" user = "root" password = "${var.root_password}" host = "${var.host}" } }
That's only a code snippet, not the full configuration, though.
Answer is A: True Multiple provisioners can be specified within a resource. Multiple provisioners are executed in the order they're defined in the configuration file. https://developer.hashicorp.com/terraform/language/resources/provisioners/syntax resource "aws_instance" "web" { # ... provisioner "local-exec" { command = "echo first" } provisioner "local-exec" { command = "echo second" } }
https://developer.hashicorp.com/terraform/language/resources/provisioners/connection Connection blocks don't take a block label and can be nested within either a resource or a provisioner. A connection block nested directly within a resource affects all of that resource's provisioners. A connection block nested in a provisioner block only affects that provisioner and overrides any resource-level connection settings. in the question they asked 'must' so may be the answer is False : B . I think so please confirm. I am confused now.
No Standalone Provisioners: Terraform does not support defining provisioners as standalone elements outside of resource blocks. All provisioner configurations must be part of a resource definition because their execution context is tightly coupled with resources. Alternatives to Provisioners: For scenarios where you might think about using provisioners in a more decoupled or independent manner, Terraform suggests other mechanisms. For instance, if the goal is to manage configuration or orchestration that seems beyond the scope of what should be tightly coupled to a single resource's lifecycle, tools like Ansible, Chef, Puppet, or Terraform itself (through resource dependencies and proper module design) are recommended to handle such configurations. These tools can be used in conjunction with Terraform but managed through their mechanisms for orchestration or configuration management, rather than through Terraform provisioners.
True provisioner should only placed under the resource block PS E:\Terraform> terraform.exe validate ╷ │ Error: Unsupported block type │ │ on main.tf line 34: │ 34: provisioner "local-exec" { │ │ Blocks of type "provisioner" are not expected here. ╵
A is the correct answer
True. Ans is A
A : True
A- True
A. If you need to run provisioners that aren't directly associated with a specific resource, you can associate them with a null_resource.
Should be B # Terraform Block terraform { required_version = ">= 1.0.0" required_providers { azurerm = { source = "hashicorp/azurerm" version = ">= 2.0" } random = { source = "hashicorp/random" version = ">= 3.0" } } } # Provider Block provider "azurerm" { features {} }
provisioner != provider
LOL this is funny