Skip to content

Latest commit

 

History

History
150 lines (104 loc) · 6.18 KB

File metadata and controls

150 lines (104 loc) · 6.18 KB
page_title subcategory description
airbyte_source_google_directory Resource - terraform-provider-airbyte
SourceGoogleDirectory Resource

airbyte_source_google_directory (Resource)

SourceGoogleDirectory Resource

Example Usage

resource "airbyte_source_google_directory" "my_source_googledirectory" {
  configuration = {
    additional_properties = "{ \"see\": \"documentation\" }"
    credentials = {
      sign_in_via_google_o_auth = {
        client_id     = "...my_client_id..."
        client_secret = "...my_client_secret..."
        refresh_token = "...my_refresh_token..."
      }
    }
  }
  definition_id = "6d56a1a1-2344-4792-8dbf-ef3c86125ff9"
  name          = "...my_name..."
  secret_id     = "...my_secret_id..."
  workspace_id  = "192bea1a-00c3-4227-ba9d-6ca81cd994fc"
}

Schema

Required

  • configuration (Attributes) The values required to configure the source. The schema for this must match the schema return by source_definition_specifications/get for the source. (see below for nested schema)
  • name (String) Name of the source e.g. dev-mysql-instance.
  • workspace_id (String)

Optional

  • definition_id (String) The UUID of the connector definition. One of configuration.sourceType or definitionId must be provided. Default: "d19ae824-e289-4b14-995a-0632eb46d246"; Requires replacement if changed.
  • secret_id (String) Optional secretID obtained through the public API OAuth redirect flow. Requires replacement if changed.

Read-Only

  • created_at (Number)
  • resource_allocation (Attributes) actor or actor definition specific resource requirements. if default is set, these are the requirements that should be set for ALL jobs run for this actor definition. it is overriden by the job type specific configurations. if not set, the platform will use defaults. these values will be overriden by configuration at the connection level. (see below for nested schema)
  • source_id (String)
  • source_type (String)

Nested Schema for configuration

Optional:

Nested Schema for configuration.credentials

Optional:

  • service_account_key (Attributes) For these scenario user should obtain service account's credentials from the Google API Console and provide delegated email. (see below for nested schema)
  • sign_in_via_google_o_auth (Attributes) For these scenario user only needs to give permission to read Google Directory data. (see below for nested schema)

Nested Schema for configuration.credentials.service_account_key

Required:

  • credentials_json (String, Sensitive) The contents of the JSON service account key. See the docs for more information on how to generate this key.
  • email (String) The email of the user, which has permissions to access the Google Workspace Admin APIs.

Nested Schema for configuration.credentials.sign_in_via_google_o_auth

Required:

  • client_id (String, Sensitive) The Client ID of the developer application.
  • client_secret (String, Sensitive) The Client Secret of the developer application.
  • refresh_token (String, Sensitive) The Token for obtaining a new access token.

Nested Schema for resource_allocation

Read-Only:

Nested Schema for resource_allocation.default

Read-Only:

  • cpu_limit (String)
  • cpu_request (String)
  • ephemeral_storage_limit (String)
  • ephemeral_storage_request (String)
  • memory_limit (String)
  • memory_request (String)

Nested Schema for resource_allocation.job_specific

Read-Only:

  • job_type (String) enum that describes the different types of jobs that the platform runs.
  • resource_requirements (Attributes) optional resource requirements to run workers (blank for unbounded allocations) (see below for nested schema)

Nested Schema for resource_allocation.job_specific.resource_requirements

Read-Only:

  • cpu_limit (String)
  • cpu_request (String)
  • ephemeral_storage_limit (String)
  • ephemeral_storage_request (String)
  • memory_limit (String)
  • memory_request (String)

Import

Import is supported using the following syntax:

In Terraform v1.5.0 and later, the import block can be used with the id attribute, for example:

import {
  to = airbyte_source_google_directory.my_airbyte_source_google_directory
  id = "..."
}

The terraform import command can be used, for example:

terraform import airbyte_source_google_directory.my_airbyte_source_google_directory "..."