https://github.com/geekmuse/terraform-provider-jumpcloud

A Terraform provider for JumpCloud
https://github.com/geekmuse/terraform-provider-jumpcloud

jumpcloud terraform terraform-provider

Last synced: 2 months ago
JSON representation

A Terraform provider for JumpCloud

• Host: GitHub
• URL: https://github.com/geekmuse/terraform-provider-jumpcloud
• Owner: geekmuse
• License: mit
• Created: 2017-01-24T03:21:17.000Z (about 8 years ago)
• Default Branch: master
• Last Pushed: 2017-08-03T12:49:10.000Z (over 7 years ago)
• Last Synced: 2024-08-04T10:08:52.773Z (6 months ago)
• Topics: jumpcloud, terraform, terraform-provider
• Language: Go
• Homepage:
• Size: 7.81 KB
• Stars: 17
• Watchers: 6
• Forks: 1
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.md

Awesome Lists containing this project

README

        
# jumpcloud-terraform-provider

A Terraform provider for [JumpCloud](https://jumpcloud.com).

As time goes on, this will implement JumpCloud's API as exposed through their [Go SDK](https://github.com/TheJumpCloud/jcapi).

## Where It Stands

Currently implemented is the creation, update, read, deletion, and import of users using the [SystemUsers interface](https://github.com/TheJumpCloud/JumpCloudAPI#system-users).

The following properties are currently implemented on a SystemUser:

*  UserName

*  FirstName

*  LastName

*  Email

*  Password

*  Sudo/PasswordlessSudo

*  AllowPublicKey/PublicKey

Importing users requires the manual addition of the `allow_public_key` and `password` fields to the state file, since they are not currently supported by the API.  An alternative to editing the state file is simply adding the parameters to the resource and running a `plan/apply`.  This will update those values with the service (and will also add them to the state file).

## Usage

There is a demonstration Terraform implementation in `main.tf`.

## Roadmap

I'd like to dig into the `ExternallyManaged` feature of SystemUsers next, though I will probably resort to tests first, now that public keys are implemented; then onto systems (which it appears will leverage Terraform's `Import` functionality as a means of creation, then Update/Delete), and SystemUser/System associations.