On 11/24/21 10:36 PM, Wei ZHOU wrote:
> Hi Wido,
>
> I think it is not good to run an environment with two ubuntu/qemu versions.
> It always happens that some cpu features are supported in the higher
> version but not supported in the older version.
> From my experience, the migration from olde
harikrishna-patnala commented on issue #17:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/17#issuecomment-981361493
Hi @synergiator, thanks for testing and reporting these issues. I see this
is a genuine issue. When the plan says acl_id to null then the provider shoul
synergiator opened a new issue #21:
URL: https://github.com/apache/cloudstack-terraform-provider/issues/21
With this code fragment,
```
resource "cloudstack_port_forward" "default" {
ip_address_id = cloudstack_ipaddress.my_ip.id
forward {
protocol = "
synergiator opened a new issue #20:
URL: https://github.com/apache/cloudstack-terraform-provider/issues/20
In the log output there is the following notification:
```
Provider "registry.terraform.io/cloudstack/cloudstack" produced an invalid
plan
for module., but we are to
synergiator opened a new issue #19:
URL: https://github.com/apache/cloudstack-terraform-provider/issues/19
Like in [this
project](https://github.com/firecow/gitlab-ci-local/commit/36dffbb71279703728f824bc86d1750baa14f40f),
it would be great to have automatic pull request suggestions from t
synergiator commented on issue #15:
URL: https://github.com/apache/cloudstack-go/issues/15#issuecomment-981060224
Strange enough, VM deployment using a unit test works, can't reproduce this
error with this SDK itself.
Based on the [mock test
](https://github.com/apache/cloudstack-go/blo
