Skip to content
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.

description and reason are not being set #90

Closed
ibiqlik opened this issue Sep 21, 2020 · 1 comment
Closed

description and reason are not being set #90

ibiqlik opened this issue Sep 21, 2020 · 1 comment

Comments

@ibiqlik
Copy link

ibiqlik commented Sep 21, 2020

vRA 7.5
Terraform v0.13.3
registry.terraform.io/vmware/vra7 v2.0.0

Describe the bug
description and reasons are not being set on the deployment

To Reproduce
Steps to reproduce the behavior:

  1. Terraform config file
resource "vra7_deployment" "this" {
  catalog_item_id       = var.catalog_item_id
  reasons               = "some reason"
  description           = "some description"
  lease_days            = 100
}
  1. Terraform command
terraform init
terraform plan
  1. Error
    No errors

Expected behavior
description and reasons are set. During terraform plan I would expect to see the value being set instead of just reading (known after apply) like the lease_days. Anyway description is not being set even after apply, everything else work as expected.

Logs

Terraform will perform the following actions:

  # vra7_deployment.this will be created
  + resource "vra7_deployment" "this" {
      + businessgroup_id   = (known after apply)
      + businessgroup_name = (known after apply)
      + catalog_item_id    = "5f476c1c-426e-45da-b4ca-183625a39e1e"
      + date_created       = (known after apply)
      + deployment_destroy = true
      + deployment_id      = (known after apply)
      + description        = (known after apply)
      + id                 = (known after apply)
      + last_updated       = (known after apply)
      + lease_days         = 100
      + lease_end          = (known after apply)
      + lease_start        = (known after apply)
      + name               = (known after apply)
      + owners             = (known after apply)
      + reasons            = (known after apply)
      + request_status     = (known after apply)
      + tenant_id          = (known after apply)
      + wait_timeout       = 15

      + resource_configuration {
          + cluster            = (known after apply)
          + component_name     = (known after apply)
          + configuration      = (known after apply)
          + instances          = (known after apply)
          + ip_address         = (known after apply)
          + parent_resource_id = (known after apply)
          + request_id         = (known after apply)
          + request_state      = (known after apply)
        }
    }

Desktop (please complete the following information):

  • OS: Running in Docker image hashicorp/terraform:0.13.3
@Prativa20
Copy link
Contributor

This has been fixed in the latest version v2.0.1

Thanks,
Prativa

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