mware / terraform-provider-vra7 Provider is considering the computed values as changes in the resource even though there is no update which has taken place about terraform-provider-vra7 HOT 6 OPEN

We're also seeing the same issue above but on provider 3.0.1

I have a commit which confirms back in Febuary we tested day amendments and it was working. Checked our our VmWare team who confirmed no changes have been made on the platform but this is now an issue.

from terraform-provider-vra7.

I'm also seeing the same issue using provider version 3.0.1.

from terraform-provider-vra7.

Looking into this issue.

@divya-goyal For day 2 operation to change lease, please do not modify lease_days. It is only for the initial provisioning of the resource. To modify the lease, add expiry_date in the main.tf file. is The instructions are given in the documentation https://github.com/vmware/terraform-provider-vra7/blob/master/website/docs/r/deployment.html.markdown

from terraform-provider-vra7.

@divya-goyal @Adam2Marsh @mmn01-sky I could not reproduce the scenario where if I do not make any change to the main.tf file, I see a diff in the plan. It is working as expected. Can you please confirm this? Also please make sure the lease_days and expiry_date is used as documented in https://github.com/vmware/terraform-provider-vra7/blob/master/website/docs/r/deployment.html.markdown

But when I modify the cpu or any property under configuration, I see a diff in the entire resource_configuration block. I am investigating this and I have also reached out to the Hashicorp terraform team.

from terraform-provider-vra7.

Any updates on this @Prativa20

from terraform-provider-vra7.

Hi I am also facing this issue. Any update @Prativa20 ?

thanks

from terraform-provider-vra7.