Fabian Mettler

@snoby I close this issue for now.

@benoitjpnet we did some changes in the last 3 weeks to the provider such as update the documentation link. So in your example, this should work: ```hcl resource "incus_instance" "forgejo"...

@stgraber I did some troubleshooting and I think the problem is that the public server with the public image is set to the protocol `incus` and therefore the Terraform provider...

It took me more time to think about it than to make the necessary code changes 😄 . But the following PR will fix this bug: https://github.com/lxc/terraform-provider-incus/pull/150

So, what’s the expected behavior here? We can keep writing the state even if we haven’t gotten the IP address from the newly created instance. Or, we can delete the...

> It can be a user error though, like not attaching a NIC or passing bad network-data. > > If the user asks us to wait for the IP, then...

@breml do you think there is a better way to handle with this situation than using `ignore_changes`?

So it would look like this: ```hcl incus_server { config = { " core.https_address" = "[::]:8443" // ... } } ```

I did some research and I'm not sure if we can configure this properly with a Terraform resource because of how Terraform works. That is, Terraform has the concept of...

> you can create, update and remove. the config, will have to have everything. > > my incus server config: > > ``` > ❯ curl -sk --cert ~/.config/incus/client.crt --key...