vladimirpetrov opened a new issue #22:
URL: https://github.com/apache/cloudstack-terraform-provider/issues/22
When there is a custom size volume resource, it triggers modification each
time you issue the 'apply' command - even though nothing has been changed in
the resource.
Here is my resource definition:
```
resource "cloudstack_disk" "volume1" {
name = "TERRAFORM_VOL1"
disk_offering = "custom"
size = 1
zone = "zone1"
}
```
According to terraform, the resource must be modified:
```
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
\# cloudstack_disk.volume1[0] will be updated in-place
~ resource "cloudstack_disk" "volume1" {
~ disk_offering = "Custom" -> "custom"
id = "4697210d-1dd6-414b-8447-405d4df6d0b8"
name = "TERRAFORM_VOL1"
tags = {}
# (4 unchanged attributes hidden)
}
```
And then the operation fails:
```
cloudstack_disk.volume1: Modifying...
[id=4697210d-1dd6-414b-8447-405d4df6d0b8]
╷
│ Error: Error changing disk offering/size for disk TERRAFORM_VOL1:
Undefined error: {"errorcode":432,"errortext":"The new disk offering requires
that a size be specified."}
│
│ with cloudstack_disk.volume1,
│ on cloudstack_disk.tf line 1, in resource "cloudstack_disk" "volume1":
│ 1: resource "cloudstack_disk" "volume1" {
│
╵
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
