You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 20, 2020. It is now read-only.
Terraform version terraform-provider-vra7 plugin version
./terraform -version
Terraform v0.12.4
provider.vra7 (unversioned)
Describe the bug
Creating a terraform config that follows the conventions found in the readme and in many online examples, it is now allowing to submit properties the request needs indicating the resource is not found in the root module.
resource "vra7_deployment" "example" {
count = 1
catalog_item_name = "JPTEST: RHEL72"
reasons = "I have some"
description = "deployment via terraform"
resource_configuration = {
testvm.cpu = 2
}
}
Terraform command
terraform plan
terraform apply
Error
Error: Reference to undeclared resource
on main.tf line 25, in resource "vra7_deployment" "example":
25: testvm.cpu = 2
A managed resource "testvm" "cpu" has not been declared in the root module.
Expected behavior
Terraform gets the catalog item, finds the testvm resource on it which is the name of the virtual machine in the blueprint, and applies the property as specified in the terraform configuration
Screenshots
Attached screenshot of vRA form that shows the testvm resource
Logs
vra-terraform.log is empty
terraform.log is attached terraform.log
Desktop (please complete the following information):
OS: Red Hat Enterprise Linux Server release 7.2 (Maipo)
Additional context
This example shows the cpu property, but the same happens for any property against the testvm resource.
The text was updated successfully, but these errors were encountered:
vRA 7.x version
vRA 7.4
Terraform version
terraform-provider-vra7 plugin version
./terraform -version
Terraform v0.12.4
Describe the bug
Creating a terraform config that follows the conventions found in the readme and in many online examples, it is now allowing to submit properties the request needs indicating the resource is not found in the root module.
To Reproduce
Steps to reproduce the behavior:
variable "username" {
}
variable "password" {
}
variable "tenant" {
}
variable "host" {
}
provider "vra7" {
username = "${var.username}"
password = "${var.password}"
tenant = "${var.tenant}"
host = "${var.host}"
insecure = false
}
resource "vra7_deployment" "example" {
count = 1
catalog_item_name = "JPTEST: RHEL72"
reasons = "I have some"
description = "deployment via terraform"
resource_configuration = {
testvm.cpu = 2
}
}
Terraform command
terraform plan
terraform apply
Error
Error: Reference to undeclared resource
on main.tf line 25, in resource "vra7_deployment" "example":
25: testvm.cpu = 2
A managed resource "testvm" "cpu" has not been declared in the root module.
Expected behavior
Terraform gets the catalog item, finds the testvm resource on it which is the name of the virtual machine in the blueprint, and applies the property as specified in the terraform configuration
Screenshots
Attached screenshot of vRA form that shows the testvm resource
Logs
vra-terraform.log is empty
terraform.log is attached
terraform.log
Desktop (please complete the following information):
Additional context
This example shows the cpu property, but the same happens for any property against the testvm resource.
The text was updated successfully, but these errors were encountered: