Closed clbouvier closed 1 month ago
With the changes from https://github.com/lxc/terraform-provider-incus/pull/63 it would be possible to do the following after we have released a new version of the provider:
terraform {
required_providers {
incus = {
source = "lxc/incus"
}
}
required_version = ">= 1.8"
}
provider "incus" {}
resource "incus_project" "project" {
name = "myproject"
config = {
"features.profiles" = true
}
}
data "incus_profile" "default" {
name = "default"
project = incus_project.project.name
}
resource "incus_profile" "project_default" {
name = "project_default"
project = incus_project.project.name
device {
type = "disk"
name = "root"
properties = {
pool = "default"
path = "/"
}
}
}
resource "incus_instance" "d1" {
profiles = [data.incus_profile.default.name, incus_profile.project_default.name]
image = "images:debian/12"
name = "d1"
}
Alternatively, you could use the following workaround already:
incus_project.myproject
and run terraform apply
first.incus_profile.default
and use terraform import incus_profile.default myproject/default
.I am closing this topic due to the merging of https://github.com/lxc/terraform-provider-incus/pull/63
returns the next error
The error is expected because incus always creates a default profile. Of course, we can change the name of the profile and working without the default profile but in this case we cannot track the "default" dynamically created. Import would not work because the profile is not known before the project creation. I can remind that other providers (aws) uses data source with the default. Would data for default profile (like data profile_default) fix the problem?