Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Terraform in Yandex Cloud
  • Getting started
  • Setting up Yandex Cloud Terraform provider authentication
  • Solution library
    • Overview
    • Release notes
          • serverless_workflow
  1. Terraform reference
  2. Resources
  3. Serverless Workflows
  4. Data Sources
  5. serverless_workflow

yandex_serverless_workflow (DataSource)

Written by
Yandex Cloud
Updated at July 9, 2026
View in Markdown

Arguments & Attributes ReferenceArguments & Attributes Reference

  • created_at (Read-Only) (String). Creation timestamp for the Workflow.
  • description (String). Description of the Workflow.
  • execution_url (Read-Only) (String). Execution URL of the Workflow.
  • express (Bool). Express execution mode.
  • folder_id (String). ID of the folder that the Workflow belongs to.
  • id (String). ID of the Workflow.
  • is_public (Bool). Ability of the Workflow to be executed without authentication.
  • labels (Map Of String). Workflow labels as key:value pairs.
  • log_options [Block]. Options for logging from the Workflow.
    • disabled (Bool). Is logging from Workflow disabled.
    • folder_id (String). ID of the folder which default logging group should be used for Workflows.
    • log_group_id (String). ID of the logging group which should be used for Workflows logs.
    • min_level (String). Minimum logs level.
      See [LogLevel.Level] for details.
  • name (Required)(String). Name of the Workflow. The name is unique within the folder.
  • network_id (String). ID of the VPC network Workflow will be executed in, in order to access private resources.
  • schedule [Block]. Workflow schedule settings.
    • cron_expression (Required)(String). Cron expression for the Workflow schedule.
    • timezone (Required)(String). Timezone for the Workflow schedule.
  • service_account_id (String). ID of the Service Account which will be used for resource access in Workflow execution.
  • specification [Block]. Specification of the Workflow
    • spec_yaml (String). Workflow specification in YAML format.
  • status (Read-Only) (String). Status of the Workflow.
  • timeouts [Block].
    • 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.
    • read (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). Read operations occur during any refresh or planning operation when refresh is enabled.
    • 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).
  • workflow_id (String). ID of the Workflow.

Was the article helpful?

Previous
serverless_eventrouter_rule
Next
serverless_workflow
© 2026 Direct Cursus Technology L.L.C.