Din Mušić

Very nice, thanks! Could you just include one container and VM test for this?

Hi @tsackit, just checking whether you are still interested in landing this change?

Closing this PR, as there has been no activity for a few months. Feel free to reach out if you decide to continue.

@stew3254 Do maybe you have a reproducer? We create a *blank state* for the instance when it is created, so Terraform should be aware of a failure and recreate the...

https://github.com/terraform-lxd/terraform-provider-lxd/pull/570 should address this, but will leave it open for now as there may be some other edge cases. @stew3254 Let me know if this solves your use-cases

Hi, the [`data "lxd_image"`](https://registry.terraform.io/providers/terraform-lxd/lxd/latest/docs/data-sources/image) is a datasource and only provides the information about an image. You should use [`resource "lxd_cached_image"`](https://registry.terraform.io/providers/terraform-lxd/lxd/latest/docs/resources/cached_image) to cache (download) an image.

So far everything seems to be working as expected. Please correct me and reopen the issue if needed.

Thanks for reporting this. The provider doesn’t currently support recursive file upload, but it’s a very reasonable feature to add.

If an empty value is used for remote, then we use whatever is specified as default remote at the `apply`. If remote is then explicitly set, we assume the location...

#570 addressed an issue where resources were not tracked (added to Terraform state) in case of an error after resource has been created. The `target` field was improved in https://github.com/terraform-lxd/terraform-provider-lxd/pull/559,...