Skip to content

Latest commit

 

History

History
130 lines (81 loc) · 4.17 KB

database_mysql.md

File metadata and controls

130 lines (81 loc) · 4.17 KB
page_title description
Linode: linode_database_mysql
Manages a Linode MySQL Database.

linode_database_mysql

~> DEPRECATION NOTICE: This resource has been deprecated. Please use linode_database_mysql_v2 for all future implementations.

Provides a Linode MySQL Database resource. This can be used to create, modify, and delete Linode MySQL Databases. For more information, see the Linode APIv4 docs.

Please keep in mind that Managed Databases can take up to an hour to provision.

Example Usage

Creating a simple MySQL database instance:

resource "linode_database_mysql" "foobar" {
  label = "mydatabase"
  engine_id = "mysql/8.0.30"
  region = "us-southeast"
  type = "g6-nanode-1"
}

Creating a complex MySQL database instance:

resource "linode_database_mysql" "foobar" {
  label = "mydatabase"
  engine_id = "mysql/8.0.30"
  region = "us-southeast"
  type = "g6-nanode-1"

  allow_list = ["0.0.0.0/0"]
  cluster_size = 3
  encrypted = true
  replication_type = "asynch"
  ssl_connection = true

  updates {
    day_of_week = "saturday"
    duration = 1
    frequency = "monthly"
    hour_of_day = 22
    week_of_month = 2
  }
}

Argument Reference

The following arguments are supported:

  • engine_id - (Required) The Managed Database engine in engine/version format. (e.g. mysql/8.0.30)

  • label - (Required) A unique, user-defined string referring to the Managed Database.

  • region - (Required) The region to use for the Managed Database.

  • type - (Required) The Linode Instance type used for the nodes of the Managed Database instance.

  • allow_list - (Optional) A list of IP addresses that can access the Managed Database. Each item can be a single IP address or a range in CIDR format. Use linode_database_access_controls to manage your allow list separately.

  • cluster_size - (Optional) The number of Linode Instance nodes deployed to the Managed Database. (default 1)

  • encrypted - (Optional) Whether the Managed Databases is encrypted. (default false)

  • replication_type - (Optional) The replication method used for the Managed Database. (none, asynch, semi_synch; default none)

    • Must be none for a single node cluster.

    • Must be asynch or semi_synch for a high availability cluster.

  • ssl_connection - (Optional) Whether to require SSL credentials to establish a connection to the Managed Database. (default false)

  • updates - (Optional) Configuration settings for automated patch update maintenance for the Managed Database.

updates

The following arguments are supported in the updates specification block:

  • day_of_week - (Required) The day to perform maintenance. (monday, tuesday, ...)

  • duration - (Required) The maximum maintenance window time in hours. (1..3)

  • frequency - (Required) Whether maintenance occurs on a weekly or monthly basis. (weekly, monthly)

  • hour_of_day - (Required) The hour to begin maintenance based in UTC time. (0..23)

  • week_of_month - (Optional) The week of the month to perform monthly frequency updates. Required for monthly frequency updates. (1..4)

Attributes Reference

In addition to all arguments above, the following attributes are exported:

  • id - The ID of the Managed Database.

  • ca_cert - The base64-encoded SSL CA certificate for the Managed Database instance.

  • created - When this Managed Database was created.

  • engine - The Managed Database engine. (e.g. mysql)

  • host_primary - The primary host for the Managed Database.

  • host_standby - The standby/private network host for the Managed Database.

  • root_password - The randomly-generated root password for the Managed Database instance.

  • root_username - The root username for the Managed Database instance.

  • status - The operating status of the Managed Database.

  • updated - When this Managed Database was last updated.

  • version - The Managed Database engine version. (e.g. v8.0.26)

Import

Linode MySQL Databases can be imported using the id, e.g.

terraform import linode_database_mysql.foobar 1234567