License: Other
provider "jamf" {
username = "xxxx"
password = "xxxx"
# "This is the full url of jamf, xxxx.jamfcloud.com"
url = "xxxx"
}
data "jamf_department" "example" {
name = "hoge"
}Full, comprehensive documentation is available on the Terraform website:
https://registry.terraform.io/providers/yohan460/jamf/latest/docs
$ gGPG_FINGERPRINT=xxx GITHUB_TOKEN="xxx" goreleaser release --rm-dist
Hi,
This is a followup of #12 to request Smart user groups and Static user groups support for resources and data sources.
Classic API Endpoint for User groups is described here:
POST request to create a new smart or static user group https://developer.jamf.com/jamf-pro/reference/createusergroupsbyidPUT request to update an smart or static user group https://developer.jamf.com/jamf-pro/reference/updateusergroupsbyidGET request to obtain smart or static user group details https://developer.jamf.com/jamf-pro/reference/findusergroupsbyidDELETE request to remove a smart or static user group https://developer.jamf.com/jamf-pro/reference/deleteusergroupsbyidEndpoint URL: https://yourServer.jamfcloud.com/JSSResource/usergroups/id/{id}
Sample request body for PUT and POST for smart user group (setting is_smart to true):
<user_group>
<name>Teachers</name>
<is_smart>true</is_smart>
<is_notify_on_change>true</is_notify_on_change>
<site>
<id>-1</id>
<name>None</name>
</site>
<criteria>
<criterion>
<name>Email Address</name>
<priority>0</priority>
<and_or>and</and_or>
<search_type>like</search_type>
<value>company.com</value>
<opening_paren>false</opening_paren>
<closing_paren>false</closing_paren>
</criterion>
</criteria>
</user_group>
Sample request body for PUT and POST for static user group (setting is_smart to false):
<user_group>
<name>Static Group</name>
<is_smart>false</is_smart>
<is_notify_on_change>false</is_notify_on_change>
<site>
<id>-1</id>
<name>None</name>
</site>
<users>
<user>
<id>1938</id>
<username>Mercy</username>
<full_name/>
<phone_number/>
<email_address>[email protected]</email_address>
</user>
<user>
<id>1939</id>
<username>Aaron</username>
<full_name/>
<phone_number/>
<email_address>[email protected]</email_address>
</user>
</users>
</user_group>
Required parameter for every type of request:
id, set to 0 for a POST request.
Sample Go code for each method is available on the pages above, but I don't have the knowledge to develop this by myself.
I hope I'm doing it the good way to ask this, and thank you for creating a PR if you find this enhancement helpful!
When you add a script in a policy, you may want to change its priority (BEFORE or AFTER).
Setting the priority of a script in a policy should be reflected in Jamf Pro.
Even if the priority is correctly defined in the plan, the result in Jamf Pro is not correct:
+ script {
+ id = "330"
+ name = (known after apply)
+ parameter4 = "googlechrome"
+ priority = "AFTER"
}
?
?
Hi,
This is a followup of #12 to request Sites support for resources and data sources.
Classic API Endpoint for Sites is described here:
POST request to create a new site https://developer.jamf.com/jamf-pro/reference/createsitebyidPUT request to update an exising site https://developer.jamf.com/jamf-pro/reference/updatesitebyidGET request to obtain site details https://developer.jamf.com/jamf-pro/reference/findsitesbyidDELETE request to remove a site https://developer.jamf.com/jamf-pro/reference/deletesitebyidEndpoint URL: https://yourServer.jamfcloud.com/JSSResource/sites/id/{id}
Sample request body for PUT and POST:
<site>
<name>Minneapolis</name>
</site>
Required parameter for every type of request:
id, set to 0 for a POST request.
Sample Go code for each method is available on the pages above, but I don't have the knowledge to develop this by myself.
I hope I'm doing it the good way to ask this, and thank you for creating a PR if you find this enhancement helpful!
Hi,
it seems like the provider has issues with the state of smart computer groups. the resource gets created in jamf, but TF seems to lose track of it.
Error: Provider produced inconsistent result after apply
When applying changes to jamf_smartComputerGroup.python_installed, 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.
Hi,
Announced in Jamf Pro 11, JCDS v2 will be available soon.
It would be nice to add API endpoint and methods when they will be available :-)
When declaring a script, it’s not possible to define the 11th parameter name.
parameter11 should exist in the scripts resources.
It’s not possible to create at this time the parameter11 attribute name in a script. Note that it exists when you add a script in a policy.
?
?
In a policy resource, I want to use a login trigger. To accomplish this, I declare trigger_login = true for that policy.
The login trigger checkbox in Jamf Pro should be ticked.
The login trigger checkbox in Jamf Pro is not ticked even though the parameter seems to be correctly taken in account in the plan:
+ general {
+ enabled = true
+ frequency = "Once per computer"
+ id = (known after apply)
+ location_user_only = false
+ name = "p_assign_user"
+ network_requirements = "Any"
+ notify_on_each_failed_retry = false
+ offline = false
+ retry_attempts = 3
+ retry_event = "check-in"
+ target_drive = "/"
+ trigger = "EVENT"
+ trigger_checkin = false
+ trigger_enrollment_complete = false
+ trigger_login = true
+ trigger_logout = false
+ trigger_network_state_changed = false
+ trigger_startup = false
?
?
Hi,
This is another request to add Icons for resources and data sources.
Jamf Pro API Endpoint for Icons is described here:
POST request to upload a new icon https://developer.jamf.com/jamf-pro/reference/post_v1-iconGET request to download an existing icon https://developer.jamf.com/jamf-pro/reference/get_v1-icon-idEndpoint URL: https://yourServer.jamfcloud.com/api/v1/icon/{id}
Sample request body for POST with cURL:
curl --request POST \
--url https://yourserver.jamfcloud.com/api/v1/icon \
--header 'accept: application/json' \
--header 'content-type: multipart/form-data' \
--form [email protected]
Required parameter for GET: id
Sample Go code for each method is available on the pages above, but I don't have the knowledge to develop this by myself.
I hope I'm doing it the good way to ask this, and thank you for creating a PR if you find this enhancement helpful!
Could we please get a new provider release so I can pull the OAuth changes added here? 5195504
I am currently finalising some Github Workflows and would like to utilise using specific Jamf API client roles for terraform plan and terraform apply jobs i.e. read only role for plan and read/write role for apply.
Hi,
This is a followup of #12 to request Network segments support for resources and data sources.
Classic API Endpoint for Network segments is described here:
POST request to create a new network segment https://developer.jamf.com/jamf-pro/reference/createnetworksegmentbyidPUT request to update an exising network segment https://developer.jamf.com/jamf-pro/reference/updatenetworksegmentbyidGET request to obtain network segment details https://developer.jamf.com/jamf-pro/reference/findnetworksegmentsbyidDELETE request to remove a network segment https://developer.jamf.com/jamf-pro/reference/deletenetworksegmentbyidEndpoint URL: https://yourServer.jamfcloud.com/JSSResource/networksegments/id/{id}
Sample request body for PUT and POST:
<network_segment>
<name>NY Office</name>
<starting_address>10.1.1.1</starting_address>
<ending_address>10.10.1.1</ending_address>
<override_buildings>false</override_buildings>
<override_departments>false</override_departments>
</network_segment>
Required parameter for every type of request:
id, set to 0 for a POST request.
Sample Go code for each method is available on the pages above, but I don't have the knowledge to develop this by myself.
I hope I'm doing it the good way to ask this, and thank you for creating a PR if you find this enhancement helpful!
Hi,
Is there a plan to migrate the communication method with Jamf Pro to the API client libraries generated by openapi-generator?
Not sure about that but it seems that this project new API URLs are https://instance.jamfcloud.com/uapi/vX/... instead of https://instance.jamfcloud.com/api/vX/...
Also: for some endpoints in new Jamf Pro API (like categories for example), there is a page size limit. I did not have any issues with that but if I remember well you could not list more than 2000 object per page (Jamf Pro limitation), and the default is 100.
Of course it could be extended to all API endpoints , but
these ones are mandatory in my opinion :
Reproducible in acc tests:
=== NAME TestAccJamfComputerExtensionAttribute_basic
resource_jamf_computer_extension_attribute_test.go:12: Step 1/3 error: Error running apply: exit status 1
Error: Provider produced inconsistent result after apply
When applying changes to
jamf_computer_extension_attribute.extensionattribute-script, provider
"provider[\"registry.terraform.io/hashicorp/jamf\"]" produced an unexpected
new value: Root object was present, but now absent.
This is a bug in the provider, which should be reported in the provider's own
issue tracker.
--- FAIL: TestAccJamfComputerExtensionAttribute_basic (1.51s)
The remote state is properly created. It seems that Jamf API returns a 404, & the object's ID is set to an empty string (60% sure). It's not clear if we're passing an erroneous ID to resourceJamfComputerExtensionAttributeRead or if the Jamf API lags (suspect latter, but need to reproduce outside tests to prove).
resource_jamf_computer_extension_attribute_test.go:12: Step 1/3 error: Error running pre-apply refresh: exit status 1
Error: expected data_type to be one of [String Integer Date], got string
with jamf_computer_extension_attribute.extensionattribute-script,
on terraform_plugin_test.tf line 4, in resource "jamf_computer_extension_attribute" "extensionattribute-script":
4: data_type = "string"
After applying successfully the whole plan, performing again terraform plan updates policies and configuration profiles despite the fact they are not modified.
Without any changes, terraform plan should display: Plan: 0 to add, 0 to change, 0 to destroy.
Without any changes, terraform plan actually display: Plan: 0 to add, 33 to change, 0 to destroy.
33 is the number of policies and configuration profiles.
Here is an output for a policy for example:
# jamf_policy.policies[15] will be updated in-place
~ resource "jamf_policy" "policies" {
id = "290"
- files_and_processes {
- delete_file = false -> null
- kill_process = false -> null
- update_locate_database = false -> null
}
+ files_and_processes {}
- general {
- enabled = true -> null
- frequency = "Once every day" -> null
- id = 290 -> null
- location_user_only = false -> null
- name = "p_update_inventory" -> null
- network_requirements = "Any" -> null
- notify_on_each_failed_retry = false -> null
- offline = false -> null
- retry_attempts = -1 -> null
- retry_event = "none" -> null
- target_drive = "/" -> null
- trigger = "CHECKIN" -> null
- trigger_checkin = true -> null
- trigger_enrollment_complete = false -> null
- trigger_login = false -> null
- trigger_logout = false -> null
- trigger_network_state_changed = false -> null
- trigger_startup = false -> null
- category {
- id = "451" -> null
- name = "Configuration" -> null
}
- network_limitations {
- any_ip_address = true -> null
- minimum_network_connection = "No Minimum" -> null
}
- override_default_settings {
- distribution_point = "default" -> null
- force_afp_smb = false -> null
- sus = "default" -> null
- target_drive = "/" -> null
}
- site {
-id = -1 ->null
- name = "None" -> null
}
}
+ general {
+ enabled = true
+ frequency = "Once every day"
+ id = (known after apply)
+ location_user_only = false
+ name = "p_update_inventory"
+ network_requirements = "Any"
+ notify_on_each_failed_retry = false
+ offline = false
+ retry_attempts = 0
+ retry_event = "none"
+ target_drive = "/"
+ trigger = "EVENT"
+ trigger_checkin = true
+ trigger_enrollment_complete = false
+ trigger_login = false
+ trigger_logout = false
+ trigger_network_state_changed = false
+ trigger_startup = false
+ category {
+ id = "451"
+ name = "Configuration"
}
+ network_limitations {
+ any_ip_address = true
+ minimum_network_connection = "No Minimum"
}
+ override_default_settings {
+ force_afp_smb = false
+ netboot_server = "current"
+ sus = "default"
+ target_drive = "default"
}
+ site {
+id = -1
+ name = (known after apply)
}
}
- self_service {
- feature_on_main_page = false -> null
- force_users_to_view_description = false -> null
- install_button_text = "Install" -> null
- reinstall_button_text = "Reinstall" -> null
- use_for_self_service = false -> null
- self_service_category {
- display_in = true -> null
- feature_in = false -> null
- id = 451 -> null
- name = "Configuration" -> null
}
- self_service_icon {
- id = 0 -> null
}
}
+ self_service {
+ feature_on_main_page = false
+ force_users_to_view_description = false
+ install_button_text = "Install"
+ reinstall_button_text = "Reinstall"
+ use_for_self_service = false
+ self_service_category {
+ id = 451
+ name = (known after apply)
}
+ self_service_icon {
+ filename = (known after apply)
+ id = 0
+ uri = (known after apply)
}
}
- user_interaction {
- allow_deferral_minutes = 0 -> null
- allow_users_to_defer = false -> null
}
+ user_interaction {}
# (3 unchanged blocks hidden)
}
Plan: 0 to add, 33 to change, 0 to destroy.
The side effect is that when I perform a terraform apply the policies and the profiles are redeployed. Below the creation and the unwanted update (see capture #1).
It’s problematic for profiles because as you can see they are redeployed to devices, which obviously is not a good idea (see capture #2).
?
?
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
}
On 1st launch terraform apply should create all resources.
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" {
│
Could be a latency in the Jamf Pro SQL database.
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.
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
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.