Publisher
cloudquery
Latest version
v1.3.2
Type
Source
Platforms
Date Published
Overview #
The CloudQuery Jamf plugin pulls data out of Jamf and loads it into any supported CloudQuery destination (e.g. PostgreSQL, BigQuery, Snowflake, and more).
Authentication #
In order to fetch information from Jamf,
cloudquery
needs to be authenticated.
An API role along with a client ID and secret are required for authentication.
See the Jamf Pro documentation for more information.Jamf Source Plugin Configuration Reference
Example #
This example syncs from Jamf to a Postgres destination.
The (top level) source spec section is described in the Source Spec Reference.
kind: source
# Common source-plugin configuration
spec:
name: jamf
path: cloudquery/jamf
registry: cloudquery
version: "v1.3.2"
tables: ["*"]
destinations: ["postgresql"]
spec:
url: "${JAMF_URL}"
client_id: "${JAMF_CLIENT_ID}"
client_secret: "${JAMF_CLIENT_SECRET}"
Jamf Spec #
This is the (nested) spec used by the LeanIX source plugin.
url
(string
) (required)Your Jamf instance URL. With or without a trailing slash.client_id
(string
) (required)A client ID for your generated API role. See: https://learn.jamf.com/en-US/bundle/jamf-pro-documentation-current/page/API_Roles_and_Clients.html.client_secret
(string
) (required)A client secret for your generated API role. See: https://learn.jamf.com/en-US/bundle/jamf-pro-documentation-current/page/API_Roles_and_Clients.html.concurrency
(integer
) (optional) (default:10
)A best effort maximum number of Go routines to use. Lower this number to reduce memory usage.scheduler
(string
) (optional) (default:dfs
) The scheduler to use when determining the priority of resources to sync. Supported values aredfs
(depth-first search),round-robin
,shuffle
andshuffle-queue
.For more information about this, see performance tuning.