Skip to content
A @hashicorp Terraform provider for managing G Suite resources.
Branch: master
Clone or download
DeviaVir bugfix: already existing member bug (#60)
* bugfix: already existing member bug

* Release v0.1.19

Signed-off-by: Chase Sillevis <>
Latest commit 31eeb64 Apr 8, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Various fixes Dec 2018 (#40) Dec 31, 2018
examples Various user fixes (#58) Mar 20, 2019
gsuite bugfix: already existing member bug (#60) Apr 8, 2019
.gitignore ignore so provider configurations can be placed along side… Dec 27, 2018
.travis.yml Update to terrafrom 0.12 (#54) Mar 18, 2019
Gopkg.lock Various user fixes (#58) Mar 20, 2019
Gopkg.toml Various user fixes (#58) Mar 20, 2019
Makefile bugfix: already existing member bug (#60) Apr 8, 2019 Domain resource (#48) Mar 15, 2019
main.go Limit scope to what we actually use (#22) May 31, 2018

Terraform G Suite Provider

This is a terraform provider for managing G Suite (Admin SDK) resources on Google


There are two possible authentication mechanisms for using this provider. Using a service account, or a personal admin account. The latter requires user interaction, whereas a service account could be used in an automated workflow.

See the necessary oauth scopes both for service accounts and users below:

You could also provide the minimal set of scopes using the oauth_scopes variable in the provider configuration.

provider "gsuite" {
  oauth_scopes = [

NOTE If you are creating or modifying schemas and custom user attributes you will need the following additional scope:

Using a service account

Service accounts are great for automated workflows.

Only users with access to the Admin APIs can access the Admin SDK Directory API, therefore the service account needs to impersonate one of those users to access the Admin SDK Directory API.

Follow the instruction at

Add credentials and impersonated_user_email when initializing the provider.

provider "gsuite" {
  credentials = "/full/path/service-account.json"
  impersonated_user_email = ""

Credentials can also be provided via the following environment variables:


Using a personal administrator account

In order to use the Admin SDK with a project, we will first need to create credentials for that project, you can do so here:[project_ID]

Please make sure to create an OAuth 2.0 client, and download the file to your local directory.

You can now use that credential to authenticate:

$ gcloud auth application-default login \
  --client-id-file=client_id.json \
  --scopes \,\,

Now that you have a credential that is allowed to the Admin SDK, you can use the G Suite provider.


  1. Download the latest compiled binary from GitHub releases.

  2. Unzip/untar the archive.

  3. Move it into $HOME/.terraform.d/plugins:

    $ mkdir -p $HOME/.terraform.d/plugins
    $ mv terraform-provider-gsuite $HOME/.terraform.d/plugins/terraform-provider-gsuite
  4. Create your Terraform configurations as normal, and run terraform init:

    $ terraform init

    This will find the plugin locally.


  1. cd into $HOME/.terraform.d/plugins/terraform-provider-gsuite

  2. Run dep ensure to fetch the go vendor files

  3. Make your changes

  4. Run make dev and in your terraform directory, remove the current .terraform and re-run terraform init

  5. Next time you run terraform plan it'll use your updated version

Relevant Google Admin SDK Documentation


Schema Types

When using a service account, make sure to add: to the oauth_scopes list, otherwise you will be missing permissions to manage user schemas.


  • Asking too many permissions right now, but rather start out with too much and tone down later on
  • Quite limited, as it is a huge API, I have only added the parts I plan on using
    • Open for PR's to extend functionality
  • Documentation is still to be written, you can refer to the examples directory for now
You can’t perform that action at this time.