Перейти к основному содержимому
selectel_dbaas_kafka_datastore_v1
Последнее изменение:

selectel_dbaas_kafka_datastore_v1

Creates and manages a Kafka datastore using public API v1. For more information about Managed Databases, see the official Selectel documentation.

Example usage⁠

resource "selectel_dbaas_kafka_datastore_v1" "datastore_1" {
  name           = "datastore-1"
  project_id     = selectel_vpc_project_v2.project_1.id
  region         = "ru-3"
  type_id        = data.selectel_dbaas_datastore_type_v1.datastore_type_1.datastore_types[0].iddatastore_types[0].id
  subnet_id      = selectel_vpc_subnet_v2.subnet.subnet_id
  node_count     = 1
  flavor {
    vcpus = 2
    ram   = 8192
    disk  = 32
  }
}

Argument Reference⁠

  • name - (Required) Datastore name. Changing this creates a new datastore.

  • project_id - (Required) Unique identifier of the associated Cloud Platform project. Changing this creates a new datastore. Retrieved from the selectel_vpc_project_v2 resource. Learn more about Cloud Platform projects.

  • region - (Required) Pool where the database is located, for example, ru-3. Changing this creates a new datastore. Learn more about available pools in the Availability matrix.

  • subnet_id - (Required) Unique identifier of the associated OpenStack network. Changing this creates a new datastore. Learn more about the openstack_networking_network_v2 resource in the official OpenStack documentation.

  • type_id - (Required) Unique identifier of the datastore type. Changing this creates a new datastore. Retrieved from the selectel_dbaas_datastore_type_v1 data source.

  • node_count - (Required) Number of nodes in the datastore. The only available value is 1. Learn more about Replication.

  • flavor_id - (Optional) Unique identifier of the flavor for the datastore. Can be skipped when flavor is set. You can retrieve information about available flavors with the selectel_dbaas_flavor_v1 data source.

  • flavor - (Optional) Flavor configuration for the datastore. You can retrieve information about available flavors with the selectel_dbaas_flavor_v1 data source. Learn more about available configurations for Kafka.

    • vcpus - (Required) Number of vCPU cores.

    • ram - (Required) Amount of RAM in MB.

    • disk - (Required) Volume size in GB.

  • firewall - (Optional) List of IP-addresses with access to the datastore.

  • config - (Optional) Configuration parameters for the datastore. You can retrieve information about available configuration parameters with the selectel_dbaas_configuration_parameter_v1 data source.

Attributes Reference⁠

  • status - Datastore status.

  • connections - DNS addresses to connect to the datastore.

Import⁠

You can import a datastore:

export OS_DOMAIN_NAME=<account_id>
export OS_USERNAME=<username>
export OS_PASSWORD=<password>
export SEL_PROJECT_ID=<selectel_project_id>
export SEL_REGION=<selectel_pool>
terraform import selectel_dbaas_kafka_datastore_v1.datastore_1 <datastore_id>

where:

  • <account_id> — Selectel account ID. The account ID is in the top right corner of the Control panel. Learn more about Registration.

  • <username> — Name of the service user. To get the name, in the top right corner of the Control panel, go to the account menu ⟶ Profile and Settings ⟶ User management ⟶ the Service users tab ⟶ copy the name of the required user. Learn more about Service users.

  • <password> — Password of the service user.

  • <selectel_project_id> — Unique identifier of the associated Cloud Platform project. To get the project ID, in the Control panel, go to Cloud Platform ⟶ project name ⟶ copy the ID of the required project. Learn more about Cloud Platform projects.

  • <selectel_pool> — Pool where the cluster is located, for example, ru-3. To get information about the pool, in the Control panel, go to Cloud Platform ⟶ Managed Databases. The pool is in the Pool column.

  • <datastore_id> — Unique identifier of the datastore, for example, b311ce58-2658-46b5-b733-7a0f418703f2. To get the datastore ID, in the Control panel, go to Cloud Platform ⟶ Managed Databases ⟶ copy the ID under the cluster name.