yandex_metastore_cluster (Resource)
Статья создана
Обновлена 13 ноября 2025 г.
Managed Metastore cluster.
Example usage
//
// Create a new Metastore Cluster.
//
resource "yandex_metastore_cluster" "my_metastore_cluster" {
name = "metastore-created-with-terraform"
subnet_ids = [yandex_vpc_subnet.a.id]
security_group_ids = [yandex_vpc_security_group.metastore-sg.id]
service_account_id = yandex_iam_service_account.for-metastore.id
cluster_config = {
resource_preset_id = "c2-m8"
}
maintenance_window = {
type = "WEEKLY"
day = "MON"
hour = 12
}
description = "My awesome Metastore"
logging = {
enabled = true
folder_id = var.folder_id
min_level = "INFO"
}
}
Schema
Required
cluster_config(Attributes) Hive Metastore cluster configuration. (see below for nested schema)name(String) The resource name.service_account_id(String) Service account with rolemanaged-metastore.integrationProvider. For more information, see documentation.subnet_ids(Set of String) The list of VPC subnets identifiers which resource is attached.
Optional
deletion_protection(Boolean) Thetruevalue means that resource is protected from accidental deletion. By default is set tofalse.description(String) The resource description.folder_id(String) The folder identifier that resource belongs to. If it is not provided, the default providerfolder-idis used.labels(Map of String) A set of key/value label pairs which assigned to resource.logging(Attributes) Cloud Logging configuration. (see below for nested schema)maintenance_window(Attributes) Configuration of window for maintenance operations. (see below for nested schema)security_group_ids(Set of String) The list of security groups applied to resource or their components.timeouts(Block, Optional) (see below for nested schema)version(String) Metastore server version.
Read-Only
created_at(String) The creation timestamp of the resource.endpoint_ip(String) IP address of Metastore server balancer endpoint.id(String) The resource identifier.network_id(String) VPC network identifier which resource is attached.status(String) Status of the cluster. Can be eitherCREATING,STARTING,RUNNING,UPDATING,STOPPING,STOPPED,ERRORorSTATUS_UNKNOWN.
Nested Schema for cluster_config
Required:
resource_preset_id(String) The identifier of the preset for computational resources available to an instance (CPU, memory etc.).
Nested Schema for logging
Required:
enabled(Boolean) Enables delivery of logs generated by Metastore to Cloud Logging.
Optional:
folder_id(String) Logs will be written to default log group of specified folder. Exactly one of the attributesfolder_idorlog_group_idshould be specified.log_group_id(String) Logs will be written to the specified log group. Exactly one of the attributesfolder_idorlog_group_idshould be specified.min_level(String) Minimum level of messages that will be sent to Cloud Logging. Can be eitherTRACE,DEBUG,INFO,WARN,ERRORorFATAL. If not set then server default is applied (currentlyINFO).
Nested Schema for maintenance_window
Optional:
day(String) Day of week for maintenance window. One ofMON,TUE,WED,THU,FRI,SAT,SUN.hour(Number) Hour of day in UTC time zone (1-24) for maintenance window.type(String) Type of maintenance window. Can be eitherANYTIMEorWEEKLY. IfWEEKLY, day and hour must be specified.
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). 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).
Import
The resource can be imported by using their resource ID. For getting the resource ID you can use Yandex Cloud Web Console
# terraform import yandex_metastore_cluster.<resource Name> <resource Id>
terraform import yandex_metastore_cluster.my_metastore_cluster <cluster-id>