With #278 the incus_server resource has been added. But as the continued discussion in #139 shows, there seems to be a need for import functionality in the incus_server resource, which is currently lacking.
The incus_server resource is kind of a special case, since the server is not something, that can be created by Terraform, since it needs to exist before Terraform is even able to communicate with Incus in the first place. But the Incus als can be configured, in particular with the config map. Therefore the way the incus_server resource works as of now is, that it only manages the keys in the config map, which are defined in the Terraform configuration (or have been configured in the past and those show up in the Terraform state). All other keys are left untouched, basically preserving potential configuration, that happened before the use of Terraform.
If someone would like to manage the complete config map of Incus, a better way would be to initially import the existing server resource and then continue from there. To allow this approach, the import functionality needs to be added to the incus_server resource.
With #278 the
incus_serverresource has been added. But as the continued discussion in #139 shows, there seems to be a need for import functionality in theincus_serverresource, which is currently lacking.The
incus_serverresource is kind of a special case, since the server is not something, that can be created by Terraform, since it needs to exist before Terraform is even able to communicate with Incus in the first place. But the Incus als can be configured, in particular with theconfigmap. Therefore the way theincus_serverresource works as of now is, that it only manages the keys in the config map, which are defined in the Terraform configuration (or have been configured in the past and those show up in the Terraform state). All other keys are left untouched, basically preserving potential configuration, that happened before the use of Terraform.If someone would like to manage the complete config map of Incus, a better way would be to initially import the existing server resource and then continue from there. To allow this approach, the import functionality needs to be added to the
incus_serverresource.