drewmullen

No, that just sets `auto_import` at the top level pool. currently you have to set `auto_import` at every level. pools, by design dont inherit any attributes from the parent pools

Harvester API returns a list of VMs deleted when you call DELETECOLLECTION. But, as you said, that action isn’t documented

highly suspect: https://github.com/harvester/harvester/blob/5ab43f02144fb8c193005905945d60cc65a73133/pkg/genswagger/rest/webservices.go#L162-L175

@rmohr I see you have at least touched the openapispec generation code... any chance you can confirm this? If you can point me in the right direction i would be...

@aburdenthehand @vladikr This appears to be a systemic problem with the doc generator. All `delete` APIs reply with status which is not accurate

correct, thank you, kit

Hello, thanks for opening this issue! We have a slightly different take on module outputs which we detailed here: https://github.com/aws-ia/terraform-aws-vpc#output-usage-examples The concepts above you mentioned can all be achieved with...

Hi thanks for opening this question. We actually use the resource [_cidr_block_association](https://github.com/aws-ia/terraform-aws-vpc/blob/main/main.tf#L47-L48). The issue probably comes from the fact that the `count` in question is a complex `local` that considers...

A fix may honestly be as easy as creating a variable `var.create_vpc` and using that instead of inferring from vpc_id == null... i can do some testing I could even...

Thanks for sharing your sample HCL. What you have is fine! Now that 4.4.2 is released i can test my fix idea... standby