search

Yohan460 / terraform-provider-jamf

Other
14 stars 10 forks source link

Submitting a lot of ressources fails #5

Closed ecanault closed 3 months ago

ecanault commented 1 year ago

Description

At this time, I submit ~80 resources of different kinds: categories, groups, scripts, policies, profiles.

Resources are declared as lists of objects (see below for categories for example) and logic is done in the main.tf file using a loop for each resource type.

terraform.tfvars file:

jamf_category_list = [
  {
    CATEGORY_NAME     = "Category #1"
    CATEGORY_PRIORITY = 1
}, {
    CATEGORY_PRIORITY = 3
  },
  {
    CATEGORY_NAME     = "Category #3"
    CATEGORY_PRIORITY = 3
}, {
    CATEGORY_PRIORITY = 20
  }
]

main.tf file:

resource "jamf_category" "categories" {
  count    = length(var.jamf_category_list)
  name     = var.jamf_category_list[count.index].CATEGORY_NAME
  priority =
var.jamf_category_list[count.index].CATEGORY_PRIORITY
}

Expected behavior

On 1st launch terraform apply should create all resources.

Actual behavior

At some point, not the same at each try, I receive the following error and applying the plan stops:

Error: Provider produced inconsistent result after apply
│
│ When applying changes to jamf_smartComputerGroup.smartGroups[9], provider "provider[\"registry.terraform.io/yohan460/jamf\"]" produced an unexpected new value: Root resource
│ was present, but now absent.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Relaunching the terraform apply command is not enough because the object has been correctly created, but terraform does not seem to be informed of this creation:

Error: API Error: 409 URI: /JSSResource/computergroups/id/0 Body: <html> <head> <title>Status page</title> </head> <body style="font-family: sans-serif;"> <p style="font-size: 1.2em;font- weight: bold;margin: 1em 0px;">Conflict</p> <p>Error: Duplicate name</p> <p>You can get technical details <a href="http://

www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.10">here</ a>.<br> Please continue your visit at our <a href="/">home page</a>. </p> </body> </html>
│
│   with jamf_smartComputerGroup.smartGroups[9],
│   on main.tf line 105, in resource "jamf_smartComputerGroup" "smartGroups":
│  105: resource "jamf_smartComputerGroup" "smartGroups" {
│

Possible explanation

Could be a latency in the Jamf Pro SQL database.

Possible fix

Perhaps slow down the creation of the objects in Jamf Pro? Especially when the object is created we need to wait a few seconds before verifying that it has been correctly created and populate the state file of terraform? I tried to add time_sleep and tried to use the -parallelism option without success.

Verbose logging

Below are the verbose logging captured from the moment where jamf_smartComputerGroup.smartGroups[9] should be created when we apply the plan the 1st time:

jamf_smartComputerGroup.smartGroups[9]: Creating...
2023-01-05T16:45:14.551+0100 [TRACE] checkPlannedChange: Verifying that actual change (action Create) matches planned change (action Create)
2023-01-05T16:45:14.551+0100 [INFO] Starting apply for jamf_smartComputerGroup.smartGroups[9] jamf_smartComputerGroup.smartGroups[2]: Creating... 2023-01-05T16:45:14.551+0100 [INFO] Starting apply for jamf_smartComputerGroup.smartGroups[2]
2023-01-05T16:45:14.551+0100 [DEBUG] jamf_smartComputerGroup.smartGroups[2]: applying the planned Create change
2023-01-05T16:45:14.551+0100 [TRACE] GRPCProvider:
ApplyResourceChange
2023-01-05T16:45:14.551+0100 [DEBUG]
jamf_smartComputerGroup.smartGroups[9]: applying the planned Create change
2023-01-05T16:45:14.551+0100 [TRACE] GRPCProvider:
ApplyResourceChange
2023-01-05T16:45:14.552+0100 [INFO]  provider.terraform-provider-
jamf_v1.0.14: 2023/01/05 16:45:14 [DEBUG] setting computed for
"computer" from ComputedKeys: timestamp=2023-01-05T16:45:14.552+0100
2023-01-05T16:45:14.552+0100 [INFO]  provider.terraform-provider-
jamf_v1.0.14: 2023/01/05 16:45:14 [DEBUG] setting computed for
"computer" from ComputedKeys: timestamp=2023-01-05T16:45:14.552+0100
2023-01-05T16:45:14.555+0100 [INFO]  provider.terraform-provider-
jamf_v1.0.14: 2023/01/05 16:45:14 [ERROR] setting state: Invalid
address to set: []string{"criteria"}:
timestamp=2023-01-05T16:45:14.555+0100
2023-01-05T16:45:14.555+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState to
workingState for jamf_staticComputerGroup.staticGroups[0]
2023-01-05T16:45:14.555+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState: writing
state object for jamf_staticComputerGroup.staticGroups[0]
2023-01-05T16:45:14.555+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState to
workingState for jamf_staticComputerGroup.staticGroups[0]
2023-01-05T16:45:14.555+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState: writing
state object for jamf_staticComputerGroup.staticGroups[0]
jamf_staticComputerGroup.staticGroups[0]: Creation complete after 1s [id=778]
2023-01-05T16:45:14.557+0100 [TRACE] vertex "jamf_staticComputerGroup.staticGroups[0]": visit complete 2023-01-05T16:45:14.557+0100 [TRACE] readDiff: Read Create change from plan for jamf_script.scripts[2]
2023-01-05T16:45:14.557+0100 [TRACE] readResourceInstanceState:
reading state for jamf_script.scripts[2]
2023-01-05T16:45:14.557+0100 [TRACE] readResourceInstanceState: no
state present for jamf_script.scripts[2]
2023-01-05T16:45:14.557+0100 [TRACE] readDiff: Read Create change
from plan for jamf_script.scripts[2]
2023-01-05T16:45:14.562+0100 [INFO] provider.terraform-provider- jamf_v1.0.14: 2023/01/05 16:45:14 [ERROR] setting state: Invalid address to set: []string{"criteria"}: timestamp=2023-01-05T16:45:14.562+0100
2023-01-05T16:45:14.562+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_staticComputerGroup.staticGroups[1] 2023-01-05T16:45:14.562+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_staticComputerGroup.staticGroups[1] 2023-01-05T16:45:14.562+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_staticComputerGroup.staticGroups[1] 2023-01-05T16:45:14.562+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_staticComputerGroup.staticGroups[1] jamf_staticComputerGroup.staticGroups[1]: Creation complete after 1s [id=781]
2023-01-05T16:45:14.563+0100 [TRACE] vertex
"jamf_staticComputerGroup.staticGroups[1]": visit complete
2023-01-05T16:45:14.563+0100 [TRACE] readDiff: Read Create change
from plan for jamf_script.scripts[1]
2023-01-05T16:45:14.563+0100 [TRACE] readResourceInstanceState:
reading state for jamf_script.scripts[1]
2023-01-05T16:45:14.563+0100 [TRACE] readResourceInstanceState: no
state present for jamf_script.scripts[1]
2023-01-05T16:45:14.563+0100 [TRACE] readDiff: Read Create change
from plan for jamf_script.scripts[1]
2023-01-05T16:45:14.564+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_smartComputerGroup.smartGroups[3] 2023-01-05T16:45:14.564+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_smartComputerGroup.smartGroups[3] 2023-01-05T16:45:14.564+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_smartComputerGroup.smartGroups[3] 2023-01-05T16:45:14.564+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_smartComputerGroup.smartGroups[3] jamf_smartComputerGroup.smartGroups[3]: Creation complete after 1s
[id=782]
2023-01-05T16:45:14.565+0100 [TRACE] vertex
"jamf_smartComputerGroup.smartGroups[3]": visit complete
2023-01-05T16:45:14.565+0100 [TRACE] readDiff: Read Create change
from plan for jamf_script.scripts[6]
2023-01-05T16:45:14.565+0100 [TRACE] readResourceInstanceState:
reading state for jamf_script.scripts[6]
2023-01-05T16:45:14.565+0100 [TRACE] readResourceInstanceState: no
state present for jamf_script.scripts[6]
2023-01-05T16:45:14.565+0100 [TRACE] readDiff: Read Create change
from plan for jamf_script.scripts[6]
2023-01-05T16:45:14.567+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_smartComputerGroup.smartGroups[6] 2023-01-05T16:45:14.567+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_smartComputerGroup.smartGroups[6] 2023-01-05T16:45:14.567+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_smartComputerGroup.smartGroups[6] 2023-01-05T16:45:14.567+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_smartComputerGroup.smartGroups[6] jamf_smartComputerGroup.smartGroups[6]: Creation complete after 1s [id=783]
2023-01-05T16:45:14.568+0100 [TRACE] vertex "jamf_smartComputerGroup.smartGroups[6]": visit complete 2023-01-05T16:45:14.568+0100 [TRACE] readDiff: Read Create change from plan for jamf_script.scripts[7]
2023-01-05T16:45:14.568+0100 [TRACE] readResourceInstanceState: reading state for jamf_script.scripts[7] 2023-01-05T16:45:14.568+0100 [TRACE] readResourceInstanceState: no state present for jamf_script.scripts[7] 2023-01-05T16:45:14.568+0100 [TRACE] readDiff: Read Create change from plan for jamf_script.scripts[7]
2023-01-05T16:45:14.594+0100 [TRACE] Re-validating config for "jamf_script.scripts[2]"
2023-01-05T16:45:14.594+0100 [TRACE] GRPCProvider: ValidateResourceConfig
2023-01-05T16:45:14.596+0100 [TRACE] GRPCProvider: PlanResourceChange
2023-01-05T16:45:14.596+0100 [TRACE] Re-validating config for "jamf_script.scripts[7]"
2023-01-05T16:45:14.596+0100 [TRACE] GRPCProvider: ValidateResourceConfig
2023-01-05T16:45:14.596+0100 [TRACE] GRPCProvider: PlanResourceChange
2023-01-05T16:45:14.596+0100 [TRACE] checkPlannedChange: Verifying that actual change (action Create) matches planned change (action Create)
jamf_script.scripts[2]: Creating...
2023-01-05T16:45:14.596+0100 [INFO] Starting apply for jamf_script.scripts[2]
2023-01-05T16:45:14.596+0100 [TRACE] Re-validating config for
"jamf_script.scripts[1]"
2023-01-05T16:45:14.596+0100 [TRACE] GRPCProvider: ValidateResourceConfig
2023-01-05T16:45:14.596+0100 [TRACE] GRPCProvider: PlanResourceChange
2023-01-05T16:45:14.597+0100 [TRACE] checkPlannedChange: Verifying that actual change (action Create) matches planned change (action Create)
jamf_script.scripts[7]: Creating...
2023-01-05T16:45:14.597+0100 [INFO] Starting apply for jamf_script.scripts[7]
2023-01-05T16:45:14.597+0100 [TRACE] checkPlannedChange: Verifying that actual change (action Create) matches planned change (action Create)
jamf_script.scripts[1]: Creating...
2023-01-05T16:45:14.597+0100 [INFO] Starting apply for jamf_script.scripts[1]
2023-01-05T16:45:14.599+0100 [TRACE] Re-validating config for "jamf_script.scripts[6]"
2023-01-05T16:45:14.599+0100 [TRACE] GRPCProvider: ValidateResourceConfig
2023-01-05T16:45:14.599+0100 [TRACE] GRPCProvider: PlanResourceChange
2023-01-05T16:45:14.599+0100 [TRACE] checkPlannedChange: Verifying that actual change (action Create) matches planned change (action Create)
jamf_script.scripts[6]: Creating...
2023-01-05T16:45:14.600+0100 [INFO] Starting apply for jamf_script.scripts[6]
2023-01-05T16:45:14.613+0100 [TRACE] maybeTainted: jamf_smartComputerGroup.smartGroups[1] encountered an error during creation, so it is now marked as tainted 2023-01-05T16:45:14.613+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_smartComputerGroup.smartGroups[1] 2023-01-05T16:45:14.613+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: removing state object for jamf_smartComputerGroup.smartGroups[1] 2023-01-05T16:45:14.613+0100 [TRACE] evalApplyProvisioners: jamf_smartComputerGroup.smartGroups[1] is tainted, so skipping provisioning
2023-01-05T16:45:14.613+0100 [TRACE] maybeTainted: jamf_smartComputerGroup.smartGroups[1] was already tainted, so nothing to do
2023-01-05T16:45:14.613+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_smartComputerGroup.smartGroups[1] 2023-01-05T16:45:14.613+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: removing state object for jamf_smartComputerGroup.smartGroups[1] 2023-01-05T16:45:14.615+0100 [ERROR] vertex "jamf_smartComputerGroup.smartGroups[1]" error: Provider produced inconsistent result after apply
2023-01-05T16:45:14.615+0100 [TRACE] vertex
"jamf_smartComputerGroup.smartGroups[1]": visit complete, with
errors
2023-01-05T16:45:14.616+0100 [TRACE] readDiff: Read Create change
from plan for jamf_smartComputerGroup.smartGroups[5]
2023-01-05T16:45:14.616+0100 [TRACE] readResourceInstanceState:
reading state for jamf_smartComputerGroup.smartGroups[5]
2023-01-05T16:45:14.616+0100 [TRACE] readResourceInstanceState: no
state present for jamf_smartComputerGroup.smartGroups[5]
2023-01-05T16:45:14.616+0100 [TRACE] readDiff: Read Create change
from plan for jamf_smartComputerGroup.smartGroups[5]
2023-01-05T16:45:14.616+0100 [TRACE] Re-validating config for
"jamf_smartComputerGroup.smartGroups[5]"
2023-01-05T16:45:14.616+0100 [TRACE] GRPCProvider:
ValidateResourceConfig
2023-01-05T16:45:14.616+0100 [INFO] provider.terraform-provider- jamf_v1.0.14: 2023/01/05 16:45:14 [WARN] Truncating attribute path of 0 diagnostics for TypeSet: timestamp=2023-01-05T16:45:14.616+0100 2023-01-05T16:45:14.616+0100 [INFO] provider.terraform-provider- jamf_v1.0.14: 2023/01/05 16:45:14 [WARN] Truncating attribute path of 0 diagnostics for TypeSet: timestamp=2023-01-05T16:45:14.616+0100 2023-01-05T16:45:14.616+0100 [TRACE] GRPCProvider: PlanResourceChange
2023-01-05T16:45:14.617+0100 [TRACE] checkPlannedChange: Verifying that actual change (action Create) matches planned change (action Create)
jamf_smartComputerGroup.smartGroups[5]: Creating... 2023-01-05T16:45:14.617+0100 [INFO] Starting apply for jamf_smartComputerGroup.smartGroups[5]
2023-01-05T16:45:14.618+0100 [DEBUG] jamf_smartComputerGroup.smartGroups[5]: applying the planned Create change
2023-01-05T16:45:14.618+0100 [TRACE] GRPCProvider: ApplyResourceChange
2023-01-05T16:45:14.618+0100 [INFO] provider.terraform-provider- jamf_v1.0.14: 2023/01/05 16:45:14 [DEBUG] setting computed for "computer" from ComputedKeys: timestamp=2023-01-05T16:45:14.618+0100 2023-01-05T16:45:14.620+0100 [DEBUG] jamf_script.scripts[7]: applying the planned Create change
2023-01-05T16:45:14.620+0100 [TRACE] GRPCProvider: ApplyResourceChange
2023-01-05T16:45:14.621+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_smartComputerGroup.smartGroups[10] 2023-01-05T16:45:14.621+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_smartComputerGroup.smartGroups[10] 2023-01-05T16:45:14.621+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_smartComputerGroup.smartGroups[10] 2023-01-05T16:45:14.621+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_smartComputerGroup.smartGroups[10] jamf_smartComputerGroup.smartGroups[10]: Creation complete after 1s [id=779]
2023-01-05T16:45:14.622+0100 [TRACE] vertex
"jamf_smartComputerGroup.smartGroups[10]": visit complete
2023-01-05T16:45:14.623+0100 [TRACE] readDiff: Read Create change
from plan for jamf_script.scripts[5]
2023-01-05T16:45:14.623+0100 [TRACE] readResourceInstanceState:
reading state for jamf_script.scripts[5]
2023-01-05T16:45:14.623+0100 [TRACE] readResourceInstanceState: no
state present for jamf_script.scripts[5]
2023-01-05T16:45:14.623+0100 [TRACE] readDiff: Read Create change
from plan for jamf_script.scripts[5]
2023-01-05T16:45:14.624+0100 [DEBUG] jamf_script.scripts[1]:
applying the planned Create change
2023-01-05T16:45:14.624+0100 [TRACE] GRPCProvider:
ApplyResourceChange
2023-01-05T16:45:14.625+0100 [DEBUG] jamf_script.scripts[6]:
applying the planned Create change
2023-01-05T16:45:14.625+0100 [TRACE] GRPCProvider:
ApplyResourceChange
2023-01-05T16:45:14.626+0100 [DEBUG] jamf_script.scripts[2]:
applying the planned Create change
2023-01-05T16:45:14.626+0100 [TRACE] GRPCProvider:
ApplyResourceChange
2023-01-05T16:45:14.634+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_smartComputerGroup.smartGroups[4] 2023-01-05T16:45:14.634+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_smartComputerGroup.smartGroups[4] 2023-01-05T16:45:14.634+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_smartComputerGroup.smartGroups[4] 2023-01-05T16:45:14.634+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_smartComputerGroup.smartGroups[4] jamf_smartComputerGroup.smartGroups[4]: Creation complete after 1s [id=785]
2023-01-05T16:45:14.634+0100 [TRACE] vertex "jamf_smartComputerGroup.smartGroups[4]": visit complete 2023-01-05T16:45:14.635+0100 [TRACE] readDiff: Read Create change from plan for jamf_smartComputerGroup.smartGroups[8] 2023-01-05T16:45:14.635+0100 [TRACE] readResourceInstanceState: reading state for jamf_smartComputerGroup.smartGroups[8] 2023-01-05T16:45:14.635+0100 [TRACE] readResourceInstanceState: no state present for jamf_smartComputerGroup.smartGroups[8] 2023-01-05T16:45:14.635+0100 [TRACE] readDiff: Read Create change from plan for jamf_smartComputerGroup.smartGroups[8] 2023-01-05T16:45:14.635+0100 [TRACE] Re-validating config for "jamf_smartComputerGroup.smartGroups[8]" 2023-01-05T16:45:14.635+0100 [TRACE] GRPCProvider: ValidateResourceConfig
2023-01-05T16:45:14.635+0100 [INFO] provider.terraform-provider- jamf_v1.0.14: 2023/01/05 16:45:14 [WARN] Truncating attribute path of 0 diagnostics for TypeSet: timestamp=2023-01-05T16:45:14.635+0100 2023-01-05T16:45:14.635+0100 [INFO] provider.terraform-provider-
jamf_v1.0.14: 2023/01/05 16:45:14 [WARN] Truncating attribute path of 0 diagnostics for TypeSet: timestamp=2023-01-05T16:45:14.635+0100 2023-01-05T16:45:14.636+0100 [TRACE] GRPCProvider: PlanResourceChange
2023-01-05T16:45:14.636+0100 [TRACE] checkPlannedChange: Verifying that actual change (action Create) matches planned change (action Create)
jamf_smartComputerGroup.smartGroups[8]: Creating... 2023-01-05T16:45:14.636+0100 [INFO] Starting apply for jamf_smartComputerGroup.smartGroups[8]
2023-01-05T16:45:14.636+0100 [DEBUG] jamf_smartComputerGroup.smartGroups[8]: applying the planned Create change
2023-01-05T16:45:14.636+0100 [TRACE] GRPCProvider: ApplyResourceChange
2023-01-05T16:45:14.637+0100 [INFO] provider.terraform-provider- jamf_v1.0.14: 2023/01/05 16:45:14 [DEBUG] setting computed for "computer" from ComputedKeys: timestamp=2023-01-05T16:45:14.637+0100 2023-01-05T16:45:14.642+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_smartComputerGroup.smartGroups[7] 2023-01-05T16:45:14.642+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_smartComputerGroup.smartGroups[7] 2023-01-05T16:45:14.642+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_smartComputerGroup.smartGroups[7] 2023-01-05T16:45:14.642+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_smartComputerGroup.smartGroups[7] jamf_smartComputerGroup.smartGroups[7]: Creation complete after 1s [id=786]
2023-01-05T16:45:14.642+0100 [TRACE] vertex "jamf_smartComputerGroup.smartGroups[7]": visit complete 2023-01-05T16:45:14.642+0100 [TRACE] readDiff: Read Create change from plan for jamf_script.scripts[3]
2023-01-05T16:45:14.642+0100 [TRACE] readResourceInstanceState: reading state for jamf_script.scripts[3] 2023-01-05T16:45:14.642+0100 [TRACE] readResourceInstanceState: no state present for jamf_script.scripts[3] 2023-01-05T16:45:14.642+0100 [TRACE] readDiff: Read Create change from plan for jamf_script.scripts[3]
2023-01-05T16:45:14.643+0100 [TRACE] Re-validating config for "jamf_script.scripts[5]"
2023-01-05T16:45:14.643+0100 [TRACE] GRPCProvider: ValidateResourceConfig
2023-01-05T16:45:14.644+0100 [TRACE] GRPCProvider: PlanResourceChange
2023-01-05T16:45:14.644+0100 [TRACE] checkPlannedChange: Verifying that actual change (action Create) matches planned change (action Create)
jamf_script.scripts[5]: Creating...
2023-01-05T16:45:14.644+0100 [INFO] Starting apply for jamf_script.scripts[5]
2023-01-05T16:45:14.665+0100 [TRACE] Re-validating config for
"jamf_script.scripts[3]"
2023-01-05T16:45:14.665+0100 [TRACE] GRPCProvider:
ValidateResourceConfig
2023-01-05T16:45:14.665+0100 [TRACE] GRPCProvider:
PlanResourceChange
2023-01-05T16:45:14.666+0100 [TRACE] checkPlannedChange: Verifying
that actual change (action Create) matches planned change (action
Create)
jamf_script.scripts[3]: Creating...
2023-01-05T16:45:14.666+0100 [INFO]  Starting apply for
jamf_script.scripts[3]
2023-01-05T16:45:14.667+0100 [DEBUG] jamf_script.scripts[5]:
applying the planned Create change
2023-01-05T16:45:14.667+0100 [TRACE] GRPCProvider:
ApplyResourceChange
2023-01-05T16:45:14.687+0100 [DEBUG] jamf_script.scripts[3]:
applying the planned Create change
2023-01-05T16:45:14.687+0100 [TRACE] GRPCProvider:
ApplyResourceChange
2023-01-05T16:45:14.770+0100 [WARN]  Provider
"provider[\"registry.terraform.io/yohan460/jamf\"]" produced an
unexpected new value for jamf_script.scripts[7], but we are
tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors
from downstream operations:
      - .parameter10: was null, but now cty.StringVal("")
      - .parameter9: was null, but now cty.StringVal("")
      - .parameter11: was null, but now cty.StringVal("")
      - .parameter8: was null, but now cty.StringVal("")
      - .info: was null, but now cty.StringVal("")
      - .notes: was null, but now cty.StringVal("")
      - .os_requirements: was null, but now cty.StringVal("")
      - .parameter6: was null, but now cty.StringVal("")
      - .parameter7: was null, but now cty.StringVal("")
2023-01-05T16:45:14.770+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_script.scripts[7] 2023-01-05T16:45:14.770+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_script.scripts[7] 2023-01-05T16:45:14.770+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_script.scripts[7] 2023-01-05T16:45:14.770+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_script.scripts[7]
jamf_script.scripts[7]: Creation complete after 0s [id=327] 2023-01-05T16:45:14.771+0100 [TRACE] vertex "jamf_script.scripts[7]": visit complete 2023-01-05T16:45:14.771+0100 [TRACE] readDiff: Read Create change from plan for jamf_script.scripts[4]
2023-01-05T16:45:14.771+0100 [TRACE] readResourceInstanceState: reading state for jamf_script.scripts[4] 
2023-01-05T16:45:14.771+0100 [TRACE] readResourceInstanceState: no
state present for jamf_script.scripts[4]
2023-01-05T16:45:14.771+0100 [TRACE] readDiff: Read Create change
from plan for jamf_script.scripts[4]
2023-01-05T16:45:14.774+0100 [TRACE] maybeTainted:
jamf_smartComputerGroup.smartGroups[9] encountered an error during
creation, so it is now marked as tainted
2023-01-05T16:45:14.774+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState to
workingState for jamf_smartComputerGroup.smartGroups[9]
2023-01-05T16:45:14.774+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState: removing
state object for jamf_smartComputerGroup.smartGroups[9]
2023-01-05T16:45:14.774+0100 [TRACE] evalApplyProvisioners:
jamf_smartComputerGroup.smartGroups[9] is tainted, so skipping
provisioning
2023-01-05T16:45:14.774+0100 [TRACE] maybeTainted:
jamf_smartComputerGroup.smartGroups[9] was already tainted, so
nothing to do
2023-01-05T16:45:14.774+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState to
workingState for jamf_smartComputerGroup.smartGroups[9]
2023-01-05T16:45:14.774+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState: removing
state object for jamf_smartComputerGroup.smartGroups[9]
2023-01-05T16:45:14.774+0100 [ERROR] vertex
"jamf_smartComputerGroup.smartGroups[9]" error: Provider produced
inconsistent result after apply
2023-01-05T16:45:14.774+0100 [TRACE] vertex
"jamf_smartComputerGroup.smartGroups[9]": visit complete, with
errors
2023-01-05T16:45:14.774+0100 [TRACE] GRPCProvider: Close
2023-01-05T16:45:14.774+0100 [DEBUG] provider.stdio: received EOF,
stopping recv loop: err="rpc error: code = Unavailable desc = error
reading from server: EOF"
2023-01-05T16:45:14.775+0100 [DEBUG] provider: plugin process
exited: path=.terraform/providers/registry.terraform.io/hashicorp/
local/2.2.3/darwin_arm64/terraform-provider-local_v2.2.3_x5
pid=40321
2023-01-05T16:45:14.775+0100 [DEBUG] provider: plugin exited
2023-01-05T16:45:14.775+0100 [TRACE] vertex
"provider[\"registry.terraform.io/hashicorp/local\"] (close)": visit
complete
2023-01-05T16:45:14.793+0100 [WARN]  Provider
"provider[\"registry.terraform.io/yohan460/jamf\"]" produced an
unexpected new value for jamf_script.scripts[1], but we are
tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors
from downstream operations:
      - .os_requirements: was null, but now cty.StringVal("")
      - .parameter6: was null, but now cty.StringVal("")
      - .parameter7: was null, but now cty.StringVal("")
      - .info: was null, but now cty.StringVal("")
      - .notes: was null, but now cty.StringVal("")
      - .parameter10: was null, but now cty.StringVal("")
      - .parameter9: was null, but now cty.StringVal("")
      - .parameter8: was null, but now cty.StringVal("")
      - .parameter11: was null, but now cty.StringVal("")
2023-01-05T16:45:14.793+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_script.scripts[1] 2023-01-05T16:45:14.793+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_script.scripts[1] 2023-01-05T16:45:14.793+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_script.scripts[1] 2023-01-05T16:45:14.793+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_script.scripts[1]
jamf_script.scripts[1]: Creation complete after 0s [id=328] 2023-01-05T16:45:14.794+0100 [TRACE] vertex "jamf_script.scripts[1]": visit complete 2023-01-05T16:45:14.796+0100 [TRACE] Re-validating config for "jamf_script.scripts[4]"
2023-01-05T16:45:14.796+0100 [TRACE] GRPCProvider: ValidateResourceConfig
2023-01-05T16:45:14.796+0100 [WARN] Provider "provider[\"registry.terraform.io/yohan460/jamf\"]" produced an unexpected new value for jamf_script.scripts[6], but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors
from downstream operations:
      - .info: was null, but now cty.StringVal("")
      - .os_requirements: was null, but now cty.StringVal("")
      - .parameter5: was null, but now cty.StringVal("")
      - .parameter6: was null, but now cty.StringVal("")
      - .parameter7: was null, but now cty.StringVal("")
      - .parameter10: was null, but now cty.StringVal("")
      - .parameter9: was null, but now cty.StringVal("")
      - .parameter11: was null, but now cty.StringVal("")
      - .parameter4: was null, but now cty.StringVal("")
      - .parameter8: was null, but now cty.StringVal("")
2023-01-05T16:45:14.796+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_script.scripts[6] 2023-01-05T16:45:14.796+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_script.scripts[6] 2023-01-05T16:45:14.796+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_script.scripts[6] 2023-01-05T16:45:14.796+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_script.scripts[6]
jamf_script.scripts[6]: Creation complete after 0s [id=329] 2023-01-05T16:45:14.797+0100 [TRACE] GRPCProvider: PlanResourceChange
2023-01-05T16:45:14.797+0100 [TRACE] vertex
"jamf_script.scripts[6]": visit complete
2023-01-05T16:45:14.797+0100 [TRACE] checkPlannedChange: Verifying
that actual change (action Create) matches planned change (action
Create)
jamf_script.scripts[4]: Creating...
2023-01-05T16:45:14.797+0100 [INFO]  Starting apply for
jamf_script.scripts[4]
2023-01-05T16:45:14.818+0100 [DEBUG] jamf_script.scripts[4]:
applying the planned Create change
2023-01-05T16:45:14.818+0100 [TRACE] GRPCProvider:
ApplyResourceChange
2023-01-05T16:45:14.839+0100 [WARN]  Provider
"provider[\"registry.terraform.io/yohan460/jamf\"]" produced an
unexpected new value for jamf_script.scripts[5], but we are
tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors
from downstream operations:
      - .notes: was null, but now cty.StringVal("")
      - .os_requirements: was null, but now cty.StringVal("")
      - .info: was null, but now cty.StringVal("")
      - .parameter10: was null, but now cty.StringVal("")
      - .parameter9: was null, but now cty.StringVal("")
      - .parameter8: was null, but now cty.StringVal("")
      - .parameter11: was null, but now cty.StringVal("")
2023-01-05T16:45:14.839+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_script.scripts[5] 2023-01-05T16:45:14.839+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_script.scripts[5] 2023-01-05T16:45:14.839+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_script.scripts[5] 2023-01-05T16:45:14.839+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_script.scripts[5]
jamf_script.scripts[5]: Creation complete after 0s [id=331] 2023-01-05T16:45:14.840+0100 [TRACE] vertex "jamf_script.scripts[5]": visit complete 2023-01-05T16:45:14.840+0100 [WARN] Provider "provider[\"registry.terraform.io/yohan460/jamf\"]" produced an unexpected new value for jamf_script.scripts[3], but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors
from downstream operations:
      - .parameter11: was null, but now cty.StringVal("")
      - .parameter8: was null, but now cty.StringVal("")
      - .info: was null, but now cty.StringVal("")
      - .notes: was null, but now cty.StringVal("")
      - .os_requirements: was null, but now cty.StringVal("")
      - .parameter6: was null, but now cty.StringVal("")
      - .parameter7: was null, but now cty.StringVal("")
      - .parameter10: was null, but now cty.StringVal("")
      - .parameter9: was null, but now cty.StringVal("")
2023-01-05T16:45:14.840+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState to
workingState for jamf_script.scripts[3]
2023-01-05T16:45:14.840+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState: writing
state object for jamf_script.scripts[3]
2023-01-05T16:45:14.841+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState to
workingState for jamf_script.scripts[3]
2023-01-05T16:45:14.841+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState: writing
state object for jamf_script.scripts[3]
jamf_script.scripts[3]: Creation complete after 0s [id=332]
2023-01-05T16:45:14.841+0100 [TRACE] vertex
"jamf_script.scripts[3]": visit complete
2023-01-05T16:45:14.855+0100 [TRACE] maybeTainted:
jamf_smartComputerGroup.smartGroups[8] encountered an error during
creation, so it is now marked as tainted
2023-01-05T16:45:14.855+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState to
workingState for jamf_smartComputerGroup.smartGroups[8]
2023-01-05T16:45:14.855+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState: removing
state object for jamf_smartComputerGroup.smartGroups[8]
2023-01-05T16:45:14.855+0100 [TRACE] evalApplyProvisioners:
jamf_smartComputerGroup.smartGroups[8] is tainted, so skipping
provisioning
2023-01-05T16:45:14.855+0100 [TRACE] maybeTainted:
jamf_smartComputerGroup.smartGroups[8] was already tainted, so
nothing to do
2023-01-05T16:45:14.855+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState to
workingState for jamf_smartComputerGroup.smartGroups[8]
2023-01-05T16:45:14.855+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState: removing
state object for jamf_smartComputerGroup.smartGroups[8]
2023-01-05T16:45:14.855+0100 [ERROR] vertex
"jamf_smartComputerGroup.smartGroups[8]" error: Provider produced
inconsistent result after apply
2023-01-05T16:45:14.855+0100 [TRACE] vertex
"jamf_smartComputerGroup.smartGroups[8]": visit complete, with
errors
2023-01-05T16:45:14.859+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState to
workingState for jamf_smartComputerGroup.smartGroups[2]
2023-01-05T16:45:14.860+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState: writing
state object for jamf_smartComputerGroup.smartGroups[2]
2023-01-05T16:45:14.860+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState to
workingState for jamf_smartComputerGroup.smartGroups[2]
2023-01-05T16:45:14.860+0100 [TRACE]
NodeAbstractResouceInstance.writeResourceInstanceState: writing
state object for jamf_smartComputerGroup.smartGroups[2]
jamf_smartComputerGroup.smartGroups[2]: Creation complete after 0s [id=789]
2023-01-05T16:45:14.860+0100 [TRACE] vertex "jamf_smartComputerGroup.smartGroups[2]": visit complete 2023-01-05T16:45:14.864+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_smartComputerGroup.smartGroups[5] 2023-01-05T16:45:14.864+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_smartComputerGroup.smartGroups[5] 2023-01-05T16:45:14.864+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_smartComputerGroup.smartGroups[5] 2023-01-05T16:45:14.864+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_smartComputerGroup.smartGroups[5] jamf_smartComputerGroup.smartGroups[5]: Creation complete after 0s [id=788]
2023-01-05T16:45:14.866+0100 [TRACE] vertex
"jamf_smartComputerGroup.smartGroups[5]": visit complete
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[4]" errored, so
skipping
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[8]" errored, so
skipping
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[11]" errored, so
skipping
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[2]" errored, so
skipping
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[5]" errored, so
skipping
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[7]" errored, so
skipping
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[0]" errored, so
skipping
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[14]" errored, so
skipping
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[10]" errored, so
skipping
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[9]" errored, so
skipping
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[6]" errored, so
skipping
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[3]" errored, so
skipping
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[12]" errored, so
skipping
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[15]" errored, so
skipping
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[16]" errored, so
skipping
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[1]" errored, so
skipping
2023-01-05T16:45:14.866+0100 [TRACE] dag/walk: upstream of
"jamf_computer_configuration_profile.profiles[13]" errored, so
skipping
2023-01-05T16:45:14.961+0100 [WARN]  Provider
"provider[\"registry.terraform.io/yohan460/jamf\"]" produced an
unexpected new value for jamf_script.scripts[2], but we are
tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors
from downstream operations:
      - .parameter6: was null, but now cty.StringVal("")
      - .parameter7: was null, but now cty.StringVal("")
      - .info: was null, but now cty.StringVal("")
      - .os_requirements: was null, but now cty.StringVal("")
      - .parameter5: was null, but now cty.StringVal("")
      - .parameter9: was null, but now cty.StringVal("")
      - .parameter10: was null, but now cty.StringVal("")
      - .parameter11: was null, but now cty.StringVal("")
      - .parameter8: was null, but now cty.StringVal("")
2023-01-05T16:45:14.961+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_script.scripts[2] 2023-01-05T16:45:14.961+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_script.scripts[2] 2023-01-05T16:45:14.961+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_script.scripts[2] 2023-01-05T16:45:14.961+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_script.scripts[2]
jamf_script.scripts[2]: Creation complete after 0s [id=330] 2023-01-05T16:45:14.962+0100 [TRACE] vertex "jamf_script.scripts[2]": visit complete 2023-01-05T16:45:14.994+0100 [WARN] Provider "provider[\"registry.terraform.io/yohan460/jamf\"]" produced an unexpected new value for jamf_script.scripts[4], but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors
from downstream operations:
      - .parameter8: was null, but now cty.StringVal("")
      - .parameter11: was null, but now cty.StringVal("")
      - .parameter4: was null, but now cty.StringVal("")
      - .os_requirements: was null, but now cty.StringVal("")
      - .parameter5: was null, but now cty.StringVal("")
      - .parameter6: was null, but now cty.StringVal("")
      - .parameter7: was null, but now cty.StringVal("")
      - .info: was null, but now cty.StringVal("")
      - .notes: was null, but now cty.StringVal("")
      - .parameter10: was null, but now cty.StringVal("")
      - .parameter9: was null, but now cty.StringVal("")
2023-01-05T16:45:14.994+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_script.scripts[4] 2023-01-05T16:45:14.994+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_script.scripts[4] 2023-01-05T16:45:14.995+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for jamf_script.scripts[4] 2023-01-05T16:45:14.995+0100 [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: writing state object for jamf_script.scripts[4]
jamf_script.scripts[4]: Creation complete after 0s [id=333] 2023-01-05T16:45:14.996+0100 [TRACE] vertex "jamf_script.scripts[4]": visit complete 2023-01-05T16:45:14.996+0100 [TRACE] dag/walk: upstream of "jamf_policy.policies[1]" errored, so skipping 2023-01-05T16:45:14.996+0100 [TRACE] dag/walk: upstream of "jamf_policy.policies[6]" errored, so skipping 2023-01-05T16:45:14.996+0100 [TRACE] dag/walk: upstream of "jamf_policy.policies[11]" errored, so skipping 2023-01-05T16:45:14.996+0100 [TRACE] dag/walk: upstream of "jamf_policy.policies[13]" errored, so skipping 2023-01-05T16:45:14.996+0100 [TRACE] dag/walk: upstream of "jamf_policy.policies[9]" errored, so skipping 2023-01-05T16:45:14.996+0100 [TRACE] dag/walk: upstream of "jamf_policy.policies[0]" errored, so skipping 2023-01-05T16:45:14.996+0100 [TRACE] dag/walk: upstream of "jamf_policy.policies[12]" errored, so skipping 2023-01-05T16:45:14.996+0100 [TRACE] dag/walk: upstream of "jamf_policy.policies[4]" errored, so skipping 2023-01-05T16:45:14.996+0100 [TRACE] dag/walk: upstream of "jamf_policy.policies[5]" errored, so skipping 2023-01-05T16:45:14.997+0100 [TRACE] dag/walk: upstream of "jamf_policy.policies[10]" errored, so skipping 2023-01-05T16:45:14.997+0100 [TRACE] dag/walk: upstream of "jamf_policy.policies[8]" errored, so skipping 2023-01-05T16:45:14.997+0100 [TRACE] dag/walk: upstream of "jamf_policy.policies[3]" errored, so skipping 2023-01-05T16:45:14.997+0100 [TRACE] dag/walk: upstream of "jamf_policy.policies[14]" errored, so skipping 2023-01-05T16:45:14.997+0100 [TRACE] dag/walk: upstream of "jamf_policy.policies[7]" errored, so skipping
2023-01-05T16:45:14.997+0100 [TRACE] dag/walk: upstream of
"jamf_policy.policies[2]" errored, so skipping
2023-01-05T16:45:14.997+0100 [TRACE] dag/walk: upstream of
"jamf_policy.policies[15]" errored, so skipping
2023-01-05T16:45:14.998+0100 [TRACE] dag/walk: upstream of
"provider[\"registry.terraform.io/yohan460/jamf\"] (close)" errored,
so skipping
2023-01-05T16:45:14.998+0100 [TRACE] dag/walk: upstream of "root"
errored, so skipping
2023-01-05T16:45:15.046+0100 [DEBUG] POST https://xxxxx/api/v4/
projects/xxx/terraform/state/default?ID=xxxxx
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to jamf_smartComputerGroup.smartGroups[9], provider "provider[\"registry.terraform.io/yohan460/jamf\"]" produced an unexpected new value: Root resource
│ was present, but now absent.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to jamf_smartComputerGroup.smartGroups[1], provider "provider[\"registry.terraform.io/yohan460/jamf\"]" produced an unexpected new value: Root resource
│ was present, but now absent.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to jamf_smartComputerGroup.smartGroups[8], provider "provider[\"registry.terraform.io/yohan460/jamf\"]" produced an unexpected new value: Root resource
│ was present, but now absent.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
2023-01-05T16:45:15.267+0100 [DEBUG] DELETE https://xxxxx/api/v4/ projects/xxx/terraform/state/default/lock 2023-01-05T16:45:15.334+0100 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = error reading from server: EOF"
2023-01-05T16:45:15.337+0100 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/yohan460/ jamf/1.0.14/darwin_arm64/terraform-provider-jamf_v1.0.14 pid=40323 2023-01-05T16:45:15.337+0100 [DEBUG] provider: plugin exited
w0de commented 3 months ago

I believe you're right that latency is the primary cause. I've started 👀ing into it.

Closing this issue as duplicate of #3 (but thank you for the logs + detail!)