terraform-provider-stackgen

sg_guild_integration_types (Data Source)

⚠️ Experimental — Lists Guild integration types from the backend provider registry, including display metadata, linked Vault subcategory, remote MCP endpoint, and default container image hints. Use this before setting sg_guild_integration.type / image so HCL matches what the environment supports.

Example Usage

# When to use: Discover valid sg_guild_integration.type values and default
# container image hints before writing integration resources.
data "sg_guild_integration_types" "all" {}

data "sg_guild_integration_types" "jira" {
  type = "jira"
}

output "integration_type_matrix" {
  value = [
    for t in data.sg_guild_integration_types.all.integration_types : {
      type       = t.type
      image_name = t.image_name
      enabled    = t.enabled
    }
  ]
}

Schema

Optional

• type (String) Optional exact integration type filter (e.g. jira or grafana).

Read-Only

• integration_types (Attributes List) Integration types available from the Guild provider registry. (see below for nested schema)

Nested Schema for integration_types

Read-Only:

• capabilities (List of String) Capability tags (e.g. observability, source-control).
• description (String) Short explanation of what this integration connects to.
• display_name (String) Human-friendly name shown in the UI.
• enabled (Boolean) Whether the type can be added in the current environment.
• icon (String) Icon or glyph identifier shown in the UI.
• image_name (String) Default container image name when the type runs as a sidecar.
• image_registry_secret (String) Vault secret name holding registry credentials for the default image.
• linked_vault_subcategory (String) Vault subcategory where secrets for this integration are stored.
• remote_endpoint (String) Upstream MCP URL for remote OAuth-backed types (no container required).
• type (String) Integration type identifier used in sg_guild_integration.type.