Jumpcloud
JumpCloud — directory + device-bound identity
weave jumpcloud
Env: JUMPCLOUD_API_KEY
Setup
Configure credentials via environment variables. We recommend sourcing them through 1Password or your secrets manager rather than committing them to the shell rc.
Official API reference
weave commands for this module are checked against the vendor's published API.
| Variable | Description | Status |
|---|---|---|
| JUMPCLOUD_API_KEY | Required for authentication. | required |
Sanity-check the wiring:
weave secrets check weave jumpcloud --help weave doctor # reports JUMPCLOUD_API_KEY status
Capabilities
What this module can do, by entity and verb. ✓
means a working CLI surface; · means
not (yet) wired.
| Entity | find | list | show | do | snapshot | diff | apply |
|---|---|---|---|---|---|---|---|
| system | · | ✓ | · | · | · | · | · |
| user | ✓ | ✓ | · | · | ✓ | ✓ | ✓ |
Commands
Every registered CLI command, grouped by verb. Each example uses placeholder arguments — substitute real values for your environment.
find (1)
find user
readFind a user by email or JumpCloud user id.
weave jumpcloud find user <identifier>
list (2)
list systems
readList managed systems (workstations/servers).
weave jumpcloud list systems <arg>
list users
readList directory users.
weave jumpcloud list users <arg>
snapshot → edit YAML →
diff → apply --yes (or confirm
interactively; apply --dry-run previews the same diff).
State kinds
Resources this module can snapshot and
diff; apply where the kind supports
live writes (see Round-trip per kind). Always run
diff before apply; use
--yes in automation after review. Files live under
.weave-state/jumpcloud/.
users
jumpcloud users — field-level apply via REST.
State file skeleton
module: jumpcloud kind: users items: - # <fields specific to this kind — see snapshot output>
Workflows
End-to-end recipes from operators who already run this module in production. Copy, adapt, and put under change-control.
Users audit
Snapshot, diff, and apply users.
weave jumpcloud snapshot users $EDITOR .weave-state/jumpcloud/users.yaml weave jumpcloud diff users weave jumpcloud apply users
Terraform parity
For each Terraform resource in the canonical provider, here's the equivalent live-API verb in weave. Use this as a migration cheat-sheet, not a 1:1 contract — weave deliberately stays in the live-state lane, not the desired-state lane.
| Terraform resource | weave equivalent |
|---|---|
| jumpcloud_users | weave jumpcloud snapshot/diff/apply users Round-trip via weave state. |
Troubleshooting & source
Run weave doctor — it reports which env
vars (including JUMPCLOUD_API_KEY) are set
and which are blank.
Re-run weave jumpcloud diff <kind>
to confirm the controller's current state, then re-snapshot
before the next apply. The driver always re-snapshots
before diffing.
The module lives at https://github.com/andy-broyles/weavewhatever/tree/main/src/weave/modules/jumpcloud. File a bug or feature request at https://github.com/andy-broyles/weavewhatever/issues.