source_sonar_cloud.md

page_title	subcategory	description
airbyte_source_sonar_cloud Resource - terraform-provider-airbyte		SourceSonarCloud Resource

airbyte_source_sonar_cloud (Resource)

SourceSonarCloud Resource

Example Usage

resource "airbyte_source_sonar_cloud" "my_source_sonarcloud" {
  configuration = {
    component_keys = [
      "{ \"see\": \"documentation\" }"
    ]
    end_date     = "YYYY-MM-DD"
    organization = "airbyte"
    start_date   = "YYYY-MM-DD"
    user_token   = "...my_user_token..."
  }
  definition_id = "7f83e02e-6105-47f7-a3a0-6864ef9074e7"
  name          = "...my_name..."
  secret_id     = "...my_secret_id..."
  workspace_id  = "331ab424-d7e5-47d4-bafa-cffcae91bac2"
}

Schema

Required

• configuration (Attributes) (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. 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)
• source_id (String)
• source_type (String)

Nested Schema for configuration

Required:

• component_keys (List of String) Comma-separated list of component keys.
• organization (String) Organization key. See here.
• user_token (String, Sensitive) Your User Token. See here. The token is case sensitive.

Optional:

• end_date (String) To retrieve issues created before the given date (inclusive).
• start_date (String) To retrieve issues created after the given date (inclusive).

Import

Import is supported using the following syntax:

terraform import airbyte_source_sonar_cloud.my_airbyte_source_sonar_cloud ""