Yandex Cloud
Поиск
Связаться с намиПодключиться
  • Истории успеха
  • Документация
  • Блог
  • Все сервисы
  • Статус работы сервисов
    • Доступны в регионе
    • Инфраструктура и сеть
    • Платформа данных
    • Контейнеры
    • Инструменты разработчика
    • Бессерверные вычисления
    • Безопасность
    • Мониторинг и управление ресурсами
    • ИИ для бизнеса
    • Бизнес-инструменты
  • Все решения
    • По отраслям
    • По типу задач
    • Экономика платформы
    • Безопасность
    • Техническая поддержка
    • Каталог партнёров
    • Обучение и сертификация
    • Облако для стартапов
    • Облако для крупного бизнеса
    • Центр технологий для общества
    • Партнёрская программа
    • Поддержка IT-бизнеса
    • Облако для фрилансеров
    • Обучение и сертификация
    • Блог
    • Документация
    • Мероприятия и вебинары
    • Контакты, чаты и сообщества
    • Идеи
    • Тарифы Yandex Cloud
    • Промоакции и free tier
    • Правила тарификации
  • Истории успеха
  • Документация
  • Блог
Проект Яндекса
© 2025 ТОО «Облачные Сервисы Казахстан»
Terraform в Yandex Cloud
  • Начало работы
  • Библиотека решений
    • Обзор
    • История изменений (англ.)
          • function
          • function_iam_binding
          • function_scaling_policy
          • function_trigger

В этой статье:

  • Example usage
  • Schema
  • Required
  • Optional
  • Read-Only
  • Nested Schema for container
  • Nested Schema for container_registry
  • Nested Schema for data_streams
  • Nested Schema for dlq
  • Nested Schema for function
  • Nested Schema for iot
  • Nested Schema for log_group
  • Nested Schema for logging
  • Nested Schema for mail
  • Nested Schema for message_queue
  • Nested Schema for object_storage
  • Nested Schema for timeouts
  • Nested Schema for timer
  • Import
  1. Справочник Terraform
  2. Ресурсы (англ.)
  3. Serverless Cloud Functions
  4. Resources
  5. function_trigger

yandex_function_trigger (Resource)

Статья создана
Yandex Cloud
Обновлена 7 августа 2025 г.
  • Example usage
  • Schema
    • Required
    • Optional
    • Read-Only
    • Nested Schema for container
    • Nested Schema for container_registry
    • Nested Schema for data_streams
    • Nested Schema for dlq
    • Nested Schema for function
    • Nested Schema for iot
    • Nested Schema for log_group
    • Nested Schema for logging
    • Nested Schema for mail
    • Nested Schema for message_queue
    • Nested Schema for object_storage
    • Nested Schema for timeouts
    • Nested Schema for timer
  • Import

Allows management of Yandex Cloud Functions Trigger.

Example usageExample usage

//
// Create a new Cloud Function Trigger.
//
resource "yandex_function_trigger" "my_trigger" {
  name        = "some_name"
  description = "any description"
  timer {
    cron_expression = "* * * * ? *"
  }
  function {
    id = "tf-test"
  }
}

SchemaSchema

RequiredRequired

  • name (String) The resource name.

OptionalOptional

  • container (Block List, Max: 1) Yandex Cloud Serverless Container settings definition for Yandex Cloud Functions Trigger. (see below for nested schema)
  • container_registry (Block List, Max: 1) Container Registry settings definition for Yandex Cloud Functions Trigger, if present. (see below for nested schema)
  • data_streams (Block List, Max: 1) Data Streams settings definition for Yandex Cloud Functions Trigger, if present. (see below for nested schema)
  • description (String) The resource description.
  • dlq (Block List, Max: 1) Dead Letter Queue (DLQ) settings definition for Yandex Cloud Functions Trigger. (see below for nested schema)
  • folder_id (String) The folder identifier that resource belongs to. If it is not provided, the default provider folder-id is used.
  • function (Block List, Max: 1) Yandex Cloud Function settings definition for Yandex Cloud Functions Trigger. (see below for nested schema)
  • iot (Block List, Max: 1) IoT settings definition for Yandex Cloud Functions Trigger, if present. Only one section iot or message_queue. (see below for nested schema)
  • labels (Map of String) A set of key/value label pairs which assigned to resource.
  • log_group (Block List, Max: 1) (see below for nested schema)
  • logging (Block List, Max: 1) Logging settings definition for Yandex Cloud Functions Trigger, if present. (see below for nested schema)
  • mail (Block List, Max: 1) Mail settings definition for Yandex Cloud Functions Trigger, if present. (see below for nested schema)
  • message_queue (Block List, Max: 1) Message Queue settings definition for Yandex Cloud Functions Trigger, if present. (see below for nested schema)
  • object_storage (Block List, Max: 1) Object Storage settings definition for Yandex Cloud Functions Trigger, if present. (see below for nested schema)
  • timeouts (Block, Optional) (see below for nested schema)
  • timer (Block List, Max: 1) Timer settings definition for Yandex Cloud Functions Trigger, if present. (see below for nested schema)

Read-OnlyRead-Only

  • created_at (String) The creation timestamp of the resource.
  • id (String) The ID of this resource.

Nested Schema for Nested Schema for container

Required:

  • id (String) Yandex Cloud Serverless Container ID for Yandex Cloud Functions Trigger.

Optional:

  • path (String) Path for Yandex Cloud Serverless Container for Yandex Cloud Functions Trigger.
  • retry_attempts (String) Retry attempts for Yandex Cloud Serverless Container for Yandex Cloud Functions Trigger.
  • retry_interval (String) Retry interval in seconds for Yandex Cloud Serverless Container for Yandex Cloud Functions Trigger.
  • service_account_id (String) Service account ID for Yandex Cloud Serverless Container for Yandex Cloud Functions Trigger.

Nested Schema for Nested Schema for container_registry

Required:

  • batch_cutoff (String) Batch Duration in seconds for Yandex Cloud Functions Trigger.
  • registry_id (String) Container Registry ID for Yandex Cloud Functions Trigger.

Optional:

  • batch_size (String) Batch Size for Yandex Cloud Functions Trigger.
  • create_image (Boolean) Boolean flag for setting create image event for Yandex Cloud Functions Trigger.
  • create_image_tag (Boolean) Boolean flag for setting create image tag event for Yandex Cloud Functions Trigger.
  • delete_image (Boolean) Boolean flag for setting delete image event for Yandex Cloud Functions Trigger.
  • delete_image_tag (Boolean) Boolean flag for setting delete image tag event for Yandex Cloud Functions Trigger.
  • image_name (String) Image name filter setting for Yandex Cloud Functions Trigger.
  • tag (String) Image tag filter setting for Yandex Cloud Functions Trigger.

Nested Schema for Nested Schema for data_streams

Required:

  • batch_cutoff (String) Batch Duration in seconds for Yandex Cloud Functions Trigger.
  • database (String) Stream database for Yandex Cloud Functions Trigger.
  • service_account_id (String) Service account ID to access data stream for Yandex Cloud Functions Trigger.
  • stream_name (String) Stream name for Yandex Cloud Functions Trigger.

Optional:

  • batch_size (String) Batch Size for Yandex Cloud Functions Trigger.

Nested Schema for Nested Schema for dlq

Required:

  • queue_id (String) ID of Dead Letter Queue for Trigger (Queue ARN).
  • service_account_id (String) Service Account ID for Dead Letter Queue for Yandex Cloud Functions Trigger.

Nested Schema for Nested Schema for function

Required:

  • id (String) Yandex Cloud Function ID.

Optional:

  • retry_attempts (String) Retry attempts for Yandex Cloud Function for Yandex Cloud Functions Trigger.
  • retry_interval (String) Retry interval in seconds for Yandex Cloud Function for Yandex Cloud Functions Trigger.
  • service_account_id (String) Service account ID for Yandex Cloud Function.
  • tag (String) Tag for Yandex Cloud Function for Yandex Cloud Functions Trigger.

Nested Schema for Nested Schema for iot

Required:

  • batch_cutoff (String) Batch Duration in seconds for Yandex Cloud Functions Trigger.
  • registry_id (String) IoT Registry ID for Yandex Cloud Functions Trigger.

Optional:

  • batch_size (String) Batch Size for Yandex Cloud Functions Trigger.
  • device_id (String) IoT Device ID for Yandex Cloud Functions Trigger.
  • topic (String) IoT Topic for Yandex Cloud Functions Trigger.

Nested Schema for Nested Schema for log_group

Required:

  • batch_cutoff (String)
  • log_group_ids (Set of String)

Optional:

  • batch_size (String)

Nested Schema for Nested Schema for logging

Required:

  • batch_cutoff (String) Batch Duration in seconds for Yandex Cloud Functions Trigger.
  • group_id (String) Logging group ID for Yandex Cloud Functions Trigger.

Optional:

  • batch_size (String) Batch Size for Yandex Cloud Functions Trigger.
  • levels (Set of String) Logging level filter setting for Yandex Cloud Functions Trigger.
  • resource_ids (Set of String) Resource ID filter setting for Yandex Cloud Functions Trigger.
  • resource_types (Set of String) Resource type filter setting for Yandex Cloud Functions Trigger.
  • stream_names (Set of String) Logging stream name filter setting for Yandex Cloud Functions Trigger.

Nested Schema for Nested Schema for mail

Required:

  • batch_cutoff (String) Batch Duration in seconds for Yandex Cloud Functions Trigger.

Optional:

  • attachments_bucket_id (String) Object Storage Bucket ID for Yandex Cloud Functions Trigger.
  • batch_size (String) Batch Size for Yandex Cloud Functions Trigger.
  • service_account_id (String) Service account ID to access object storage for Yandex Cloud Functions Trigger.

Nested Schema for Nested Schema for message_queue

Required:

  • batch_cutoff (String) Batch Duration in seconds for Yandex Cloud Functions Trigger.
  • queue_id (String) Message Queue ID for Yandex Cloud Functions Trigger.
  • service_account_id (String) Message Queue Service Account ID for Yandex Cloud Functions Trigger.

Optional:

  • batch_size (String) Batch Size for Yandex Cloud Functions Trigger.
  • visibility_timeout (String) Visibility timeout for Yandex Cloud Functions Trigger.

Nested Schema for Nested Schema for object_storage

Required:

  • batch_cutoff (String) Batch Duration in seconds for Yandex Cloud Functions Trigger.
  • bucket_id (String) Object Storage Bucket ID for Yandex Cloud Functions Trigger.

Optional:

  • batch_size (String) Batch Size for Yandex Cloud Functions Trigger.
  • create (Boolean) Boolean flag for setting create event for Yandex Cloud Functions Trigger.
  • delete (Boolean) Boolean flag for setting delete event for Yandex Cloud Functions Trigger.
  • prefix (String) Prefix for Object Storage for Yandex Cloud Functions Trigger.
  • suffix (String) Suffix for Object Storage for Yandex Cloud Functions Trigger.
  • update (Boolean) Boolean flag for setting update event for Yandex Cloud Functions Trigger.

Nested Schema for Nested Schema for timeouts

Optional:

  • create (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
  • delete (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
  • update (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).

Nested Schema for Nested Schema for timer

Required:

  • cron_expression (String) Cron expression for timer for Yandex Cloud Functions Trigger.

Optional:

  • payload (String) Payload to be passed to function.

ImportImport

The resource can be imported by using their resource ID. For getting the resource ID you can use Yandex Cloud Web Console or YC CLI.

# terraform import yandex_function_trigger.<resource Name> <resource Id>
terraform import yandex_function_trigger.my_trigger a1scn**********3ur32

Была ли статья полезна?

Предыдущая
function_scaling_policy
Следующая
serverless_container
Проект Яндекса
© 2025 ТОО «Облачные Сервисы Казахстан»