Skip to content
This repository has been archived by the owner on Nov 20, 2020. It is now read-only.

Apply does not change the number of VMs created by the vRA blueprint #165

Open
spbarbieri opened this issue Feb 18, 2020 · 2 comments
Open

Comments

@spbarbieri
Copy link

I have a vRA blueprint that contains a cluster of 1 to 5 EC2 Servers:

image

I have a terraform configuration that deploys this blueprint

resource "vra7_deployment" "min_max" {
  wait_timeout = "20"
  catalog_item_name = "min-max"

  resource_configuration = {
    EC2_Cluster._cluster = "3"
    EC2_Cluster.ip_address = ""
  }
}

This successfully deploys my blueprint and creates 3 VMs.

If I change EC2_Cluster._cluster = "3" to EC2_Cluster._cluster = "5" and run Terraform apply the apply completes successfully but does nothing. I don't get 2 new VMs.

Is this expected? Am I doing something incorrectly?

@Prativa20
Copy link
Contributor

@spbarbieri
This project has moved to the terraform-providers organization and is archived.
The new location is here: https://github.com/terraform-providers/terraform-provider-vra7

About the issue, this is a day 2 scale out action which is not supported currently. Please open a feature request here https://github.com/terraform-providers/terraform-provider-vra7 and we will work on it.

Thanks,
Prativa

@spbarbieri
Copy link
Author

@Prativa20 Thanks for the information. I opened issue vmware/terraform-provider-vra#155 and was directed to this repository. I opened issue https://github.com/terraform-providers/terraform-provider-vra7/issues/47 for this request. I couldn't assign labels so I put "Feature Request" in the title.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants