Open kevingrismore opened 2 days ago
Hmm, will need to dig into this further but this does seem related to https://github.com/PrefectHQ/terraform-provider-prefect/pull/249. The JSON object gets rearranged a bit between what a user defines and what's actually stored in Prefect, causing Terraform to think the object is different. That PR helps account for the difference, but this might be an edge case.
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
When importing an existing work pool with
terraform import prefect_work_pool.k8s-demo <workspace-id>,k8s-demo
, if my work pool resource in the .tf above and the contents of the base template JSON in the referenced file are the same,plan
should detect no changes andapply
should do nothing.Actual Behavior
terraform plan
Steps to Reproduce
prefect_work_pool
"k8s-demo" resource with matching definition and reference to base job template to.tf
terraform import prefect_work_pool.k8s-demo <workspace-id>,k8s-demo
terraform plan
Important Factoids
References