Din Mušić

Hi, thanks for opening an issue. > There seems to be some cyclical dependency between the volume and the instance. You can't create the instance without the volume, and you...

The `(resource/data)_instance_device` is available now on main branch. It is tagged as experimental and may change in the future.

I'm closing this issue as stale. We cannot reproduce the issue where changing the volume size would require the volume to be recreated, but feel free to reopen the issue...

Hi, could you share the provider's terraform configuration (`provider "lxd" {...}`)?

Hmm, client certificates are generated by the LXD client, not the Terraform provider. Which LXD version is being used?

> Do you mean the certificate should be generated by LXD client instead of Terraform provider LXD? Or did you just comment on the terraform provider code above? Just commented...

Thanks. We are calling [GenerateClientCertificate](https://github.com/canonical/lxd/blob/651efd377f1bd432ae122182a410a09481430816/lxc/config/cert.go#L22-L32) from the Terraform provider, which effectively stores the certificate generated by [GenerateMemCert](https://github.com/canonical/lxd/blob/651efd377f1bd432ae122182a410a09481430816/shared/cert.go#L344) into the give path (if certificate is missing in the first place).

Hi, I've tried to reproduce the issue by installing Terraform in a Docker (Alpine) container and create an instance on remote server. I've only installed Terraform in the container -...

I am closing this one as we could not reproduce it, feel free to reopen it if the issue persists.

> Why not just change the memory settings and let the user reboot by hand ? The provider actually tries to do that, but LXD reports an error. However, it...