Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • 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
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Terraform in Yandex Cloud
  • Getting started
  • Solution library
    • Overview
    • Release notes
          • mdb_greenplum_cluster
          • mdb_greenplum_resource_group
          • mdb_greenplum_user

In this article:

  • Example usage
  • Schema
  • Required
  • Optional
  • Read-Only
  • Nested Schema for timeouts
  1. Terraform reference
  2. Resources
  3. Managed Service for Greenplum
  4. Data Sources
  5. mdb_greenplum_resource_group

yandex_mdb_greenplum_resource_group (Data Source)

Written by
Yandex Cloud
Updated at September 11, 2025
  • Example usage
  • Schema
    • Required
    • Optional
    • Read-Only
    • Nested Schema for timeouts

Get information about a greenplum resource group.

Example usageExample usage

//
// Get information about existing MDB Greenplum database resource group.
//
data "yandex_mdb_greenplum_resource_group" "my_resource_group" {
  cluster_id = "some_cluster_id"
  name       = "test"
}

output "concurrency" {
  value = data.yandex_mdb_greenplum_resource_group.my_resource_group.concurrency
}

SchemaSchema

RequiredRequired

  • cluster_id (String) The ID of the cluster to which resource group belongs to.
  • name (String) The name of the resource group.

OptionalOptional

  • timeouts (Attributes) (see below for nested schema)

Read-OnlyRead-Only

  • concurrency (Number)
  • cpu_rate_limit (Number)
  • id (String) The resource identifier.
  • is_user_defined (Boolean) If false, the resource group is immutable and controlled by yandex
  • memory_limit (Number)
  • memory_shared_quota (Number)
  • memory_spill_ratio (Number)

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).

Was the article helpful?

Previous
mdb_greenplum_cluster
Next
mdb_greenplum_user
© 2025 Direct Cursus Technology L.L.C.