terraform-provider-jamfpro icon indicating copy to clipboard operation
terraform-provider-jamfpro copied to clipboard

Jamf Pro Terraform Provider/Plugin written with the TF Provider SDK v2. Written in go

Results 20 terraform-provider-jamfpro issues
Sort by recently updated
recently updated
newest added

* Adds `install` and `build_override` rules to makefile. I've been using these during local dev to make my life easier. The idea is to run `make install` to quickly update...

Relevant jamf API docs: https://developer.jamf.com/jamf-pro/reference/get_v1-managed-software-updates-available-updates Why? While this functionality in jamf is still tagged as `beta`, Apple has made some serious improvements to the reliability of managed software updates, particularly...

Bumps [hashicorp/ghaction-terraform-provider-release](https://github.com/hashicorp/ghaction-terraform-provider-release) from 3.0.1 to 4.0.0. Release notes Sourced from hashicorp/ghaction-terraform-provider-release's releases. v4.0.0 NOTES: hashicorp: Prevent NodeJS 16 deprecation warnings by upgrading dependencies (#88) Changelog Sourced from hashicorp/ghaction-terraform-provider-release's changelog. 4.0.0...

dependencies
github_actions

Relevant jamf API docs (classic): https://developer.jamf.com/jamf-pro/reference/restrictedsoftware Why? Because managing anything manually is frustrating! 🤣 Joking aside, I'd like for my team or others to be able to add/change/remove restricted software...

Bumps [github.com/hashicorp/terraform-plugin-docs](https://github.com/hashicorp/terraform-plugin-docs) from 0.19.1 to 0.19.2. Release notes Sourced from github.com/hashicorp/terraform-plugin-docs's releases. v0.19.2 BUG FIXES: migrate: Ensured idempotency of template files when command is ran multiple times (#364) generate: Prevented...

dependencies
go

Receiving an error about being unable to update Computer Groups created with older versions of the provider. The error message refers to not being able to have the `computers` dict...

Receiving the following error when trying to create a Jamf Policy ``` Error: Invalid address to set: []string{"self_service", "0", "self_service_categories", "0", "id"} │ │ with jamfpro_policy.enrolment, │ on policy_enrolment.tf line...

I'm having a look at the recent changes to the Computer Group resource and curious about the logic behind some of the validation. Within `computergroups_state.go`, why are setting the `computers`...

I believe configuration profiles' assign computer group IDs are sorted in the API response by group ID. This diff should be suppressed. Eg: ``` # jamfpro_macos_configuration_profile.munki_shard_1 will be updated in-place...

Hi, Not a must have, but could be useful for MSP instances where you need to update the Jamf Pro activation code monthly. Thanks! Emmanuel