google.cloud.gcp_sql_instance module – Creates a GCP Instance
Note
This module is part of the google.cloud collection (version 1.4.1).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install google.cloud
.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: google.cloud.gcp_sql_instance
.
Note
The google.cloud collection will be removed from Ansible 12 due to violations of the Ansible inclusion requirements. The collection has unresolved sanity test failures. See the discussion thread for more information.
Synopsis
Represents a Cloud SQL instance. Cloud SQL instances are SQL databases hosted in Google’s cloud. The Instances resource provides methods for common configuration and management tasks.
Requirements
The below requirements are needed on the host that executes this module.
python >= 2.6
requests >= 2.18.4
google-auth >= 1.3.0
Parameters
Parameter |
Comments |
---|---|
An OAuth2 access token if credential type is accesstoken. |
|
The type of credential used. Choices:
|
|
* FIRST_GEN: First Generation instance. MySQL only. * SECOND_GEN: Second Generation instance or PostgreSQL instance. * EXTERNAL: A database server that is not managed by Google. Some valid choices include: “FIRST_GEN”, “SECOND_GEN”, “EXTERNAL” |
|
Connection name of the Cloud SQL instance used in connection strings. |
|
The database engine type and version. For First Generation instances, can be MYSQL_5_5, or MYSQL_5_6. For Second Generation instances, can be MYSQL_5_6 or MYSQL_5_7. Defaults to MYSQL_5_6. PostgreSQL instances: POSTGRES_9_6 The databaseVersion property can not be changed after instance creation. Some valid choices include: “MYSQL_5_5”, “MYSQL_5_6”, “MYSQL_5_7”, “POSTGRES_9_6” |
|
Disk encryption settings. |
|
The KMS key used to encrypt the Cloud SQL instance . |
|
Disk encryption status. |
|
The KMS key version used to encrypt the Cloud SQL instance . |
|
Specifies which Ansible environment you’re running this module within. This should not be set unless you know what you’re doing. This only alters the User Agent string for any API requests. |
|
The name and status of the failover replica. This property is applicable only to Second Generation instances. |
|
The name of the failover replica. If specified at instance creation, a failover replica is created for the instance. The name doesn’t include the project ID. This property is applicable only to Second Generation instances. |
|
The instance type. This can be one of the following. * CLOUD_SQL_INSTANCE: A Cloud SQL instance that is not replicating from a master. * ON_PREMISES_INSTANCE: An instance running on the customer’s premises. * READ_REPLICA_INSTANCE: A Cloud SQL instance configured as a read-replica. Some valid choices include: “CLOUD_SQL_INSTANCE”, “ON_PREMISES_INSTANCE”, “READ_REPLICA_INSTANCE” |
|
The IPv6 address assigned to the instance. This property is applicable only to First Generation instances. |
|
The name of the instance which will act as master in the replication setup. |
|
The maximum disk size of the instance in bytes. |
|
Name of the Cloud SQL instance. This does not include the project ID. |
|
The Google Cloud Platform project to use. |
|
The geographical region. Defaults to us-central or us-central1 depending on the instance type (First Generation or Second Generation/PostgreSQL). |
|
Configuration specific to failover replicas and read replicas. |
|
Specifies if the replica is the failover target. If the field is set to true the replica will be designated as a failover replica. In case the master instance fails, the replica instance will be promoted as the new master instance. Only one replica can be specified as failover target, and the replica has to be in different zone with the master instance. Choices:
|
|
MySQL specific configuration when replicating from a MySQL on-premises master. Replication configuration information such as the username, password, certificates, and keys are not stored in the instance metadata. The configuration information is used only to set up the replication connection and is stored by MySQL in a file named master.info in the data directory. |
|
PEM representation of the trusted CA’s x509 certificate. |
|
PEM representation of the replica’s x509 certificate . |
|
PEM representation of the replica’s private key. The corresponding public key is encoded in the client’s certificate. |
|
Seconds to wait between connect retries. MySQL’s default is 60 seconds. |
|
Path to a SQL dump file in Google Cloud Storage from which the replica instance is to be created. The URI is in the form gs://bucketName/fileName. Compressed gzip files (.gz) are also supported. Dumps should have the binlog coordinates from which replication should begin. This can be accomplished by setting –master-data to 1 when using mysqldump. |
|
Interval in milliseconds between replication heartbeats. |
|
The password for the replication connection. |
|
A list of permissible ciphers to use for SSL encryption. |
|
The username for the replication connection. |
|
Whether or not to check the master’s Common Name value in the certificate that it sends during the SSL handshake. Choices:
|
|
The replicas of the instance. |
|
The service account email address assigned to the instance. This property is applicable only to Second Generation instances. |
|
Array of scopes to be used |
|
The contents of a Service Account JSON file, either in a dictionary or as a JSON string that represents it. |
|
An optional service account email address if machineaccount is selected and the user does not wish to use the default email. |
|
The path of a Service Account JSON file if serviceaccount is selected as type. |
|
The user settings. |
|
The availabilityType define if your postgres instance is run zonal or regional. Some valid choices include: “ZONAL”, “REGIONAL” |
|
The daily backup configuration for the instance. |
|
Whether binary log is enabled. If backup configuration is disabled, binary log must be disabled as well. MySQL only. Choices:
|
|
Enable Autobackup for your instance. Choices:
|
|
Define the backup start time in UTC (HH:MM) . |
|
The database flags passed to the instance at startup. |
|
The name of the flag. These flags are passed at instance startup, so include both server options and system variables for MySQL. Flags should be specified with underscores, not hyphens. |
|
The value of the flag. Booleans should be set to on for true and off for false. This field must be omitted if the flag doesn’t take a value. |
|
The settings for IP Management. This allows to enable or disable the instance IP and manage which external networks can connect to the instance. The IPv4 address cannot be disabled for Second Generation instances. |
|
The list of external networks that are allowed to connect to the instance using the IP. In CIDR notation, also known as ‘slash’ notation (e.g. 192.168.100.0/24). |
|
The time when this access control entry expires in RFC 3339 format, for example 2012-11-15T16:19:00.094Z. |
|
An optional label to identify this entry. |
|
The whitelisted value for the access control list. For example, to grant access to a client from an external IP (IPv4 or IPv6) address or subnet, use that address or subnet here. |
|
Whether the instance should be assigned an IP address or not. Choices:
|
|
The resource link for the VPC network from which the Cloud SQL instance is accessible for private IP (e.g /projects/myProject/global/networks/default) |
|
Whether the mysqld should default to ‘REQUIRE X509’ for users connecting over IP. Choices:
|
|
The tier or machine type for this instance, for example db-n1-standard-1. For MySQL instances, this field determines whether the instance is Second Generation (recommended) or First Generation. |
|
User-provided labels, represented as a dictionary where each label is a single key value pair. |
|
Whether the given object should exist in GCP Choices:
|
Examples
- name: create a instance
google.cloud.gcp_sql_instance:
name: "{{resource_name}}-2"
settings:
ip_configuration:
authorized_networks:
- name: google dns server
value: 8.8.8.8/32
tier: db-n1-standard-1
region: us-central1
project: test_project
auth_kind: serviceaccount
service_account_file: "/tmp/auth.pem"
state: present
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
* FIRST_GEN: First Generation instance. MySQL only. * SECOND_GEN: Second Generation instance or PostgreSQL instance. * EXTERNAL: A database server that is not managed by Google. Returned: success |
|
Connection name of the Cloud SQL instance used in connection strings. Returned: success |
|
The database engine type and version. For First Generation instances, can be MYSQL_5_5, or MYSQL_5_6. For Second Generation instances, can be MYSQL_5_6 or MYSQL_5_7. Defaults to MYSQL_5_6. PostgreSQL instances: POSTGRES_9_6 The databaseVersion property can not be changed after instance creation. Returned: success |
|
Disk encryption settings. Returned: success |
|
The KMS key used to encrypt the Cloud SQL instance . Returned: success |
|
Disk encryption status. Returned: success |
|
The KMS key version used to encrypt the Cloud SQL instance . Returned: success |
|
The name and status of the failover replica. This property is applicable only to Second Generation instances. Returned: success |
|
The availability status of the failover replica. A false status indicates that the failover replica is out of sync. The master can only failover to the failover replica when the status is true. Returned: success |
|
The name of the failover replica. If specified at instance creation, a failover replica is created for the instance. The name doesn’t include the project ID. This property is applicable only to Second Generation instances. Returned: success |
|
The Compute Engine zone that the instance is currently serving from. This value could be different from the zone that was specified when the instance was created if the instance has failed over to its secondary zone. Returned: success |
|
The instance type. This can be one of the following. * CLOUD_SQL_INSTANCE: A Cloud SQL instance that is not replicating from a master. * ON_PREMISES_INSTANCE: An instance running on the customer’s premises. * READ_REPLICA_INSTANCE: A Cloud SQL instance configured as a read-replica. Returned: success |
|
The assigned IP addresses for the instance. Returned: success |
|
The IP address assigned. Returned: success |
|
The due time for this IP to be retired in RFC 3339 format, for example 2012-11-15T16:19:00.094Z. This field is only available when the IP is scheduled to be retired. Returned: success |
|
The type of this IP address. A PRIMARY address is an address that can accept incoming connections. An OUTGOING address is the source address of connections originating from the instance, if supported. Returned: success |
|
The IPv6 address assigned to the instance. This property is applicable only to First Generation instances. Returned: success |
|
The name of the instance which will act as master in the replication setup. Returned: success |
|
The maximum disk size of the instance in bytes. Returned: success |
|
Name of the Cloud SQL instance. This does not include the project ID. Returned: success |
|
The geographical region. Defaults to us-central or us-central1 depending on the instance type (First Generation or Second Generation/PostgreSQL). Returned: success |
|
Configuration specific to failover replicas and read replicas. Returned: success |
|
Specifies if the replica is the failover target. If the field is set to true the replica will be designated as a failover replica. In case the master instance fails, the replica instance will be promoted as the new master instance. Only one replica can be specified as failover target, and the replica has to be in different zone with the master instance. Returned: success |
|
MySQL specific configuration when replicating from a MySQL on-premises master. Replication configuration information such as the username, password, certificates, and keys are not stored in the instance metadata. The configuration information is used only to set up the replication connection and is stored by MySQL in a file named master.info in the data directory. Returned: success |
|
PEM representation of the trusted CA’s x509 certificate. Returned: success |
|
PEM representation of the replica’s x509 certificate . Returned: success |
|
PEM representation of the replica’s private key. The corresponding public key is encoded in the client’s certificate. Returned: success |
|
Seconds to wait between connect retries. MySQL’s default is 60 seconds. Returned: success |
|
Path to a SQL dump file in Google Cloud Storage from which the replica instance is to be created. The URI is in the form gs://bucketName/fileName. Compressed gzip files (.gz) are also supported. Dumps should have the binlog coordinates from which replication should begin. This can be accomplished by setting –master-data to 1 when using mysqldump. Returned: success |
|
Interval in milliseconds between replication heartbeats. Returned: success |
|
The password for the replication connection. Returned: success |
|
A list of permissible ciphers to use for SSL encryption. Returned: success |
|
The username for the replication connection. Returned: success |
|
Whether or not to check the master’s Common Name value in the certificate that it sends during the SSL handshake. Returned: success |
|
The replicas of the instance. Returned: success |
|
The service account email address assigned to the instance. This property is applicable only to Second Generation instances. Returned: success |
|
SSL configuration. Returned: success |
|
PEM representation of the X.509 certificate. Returned: success |
|
Serial number, as extracted from the certificate. Returned: success |
|
User supplied name. Constrained to [a-zA-Z.-_ ]+. Returned: success |
|
The time when the certificate was created in RFC 3339 format, for example 2012-11-15T16:19:00.094Z. Returned: success |
|
The time when the certificate expires in RFC 3339 format, for example 2012-11-15T16:19:00.094Z. Returned: success |
|
SHA-1 fingerprint of the certificate. Returned: success |
|
The user settings. Returned: success |
|
The availabilityType define if your postgres instance is run zonal or regional. Returned: success |
|
The daily backup configuration for the instance. Returned: success |
|
Whether binary log is enabled. If backup configuration is disabled, binary log must be disabled as well. MySQL only. Returned: success |
|
Enable Autobackup for your instance. Returned: success |
|
Define the backup start time in UTC (HH:MM) . Returned: success |
|
The database flags passed to the instance at startup. Returned: success |
|
The name of the flag. These flags are passed at instance startup, so include both server options and system variables for MySQL. Flags should be specified with underscores, not hyphens. Returned: success |
|
The value of the flag. Booleans should be set to on for true and off for false. This field must be omitted if the flag doesn’t take a value. Returned: success |
|
The settings for IP Management. This allows to enable or disable the instance IP and manage which external networks can connect to the instance. The IPv4 address cannot be disabled for Second Generation instances. Returned: success |
|
The list of external networks that are allowed to connect to the instance using the IP. In CIDR notation, also known as ‘slash’ notation (e.g. 192.168.100.0/24). Returned: success |
|
The time when this access control entry expires in RFC 3339 format, for example 2012-11-15T16:19:00.094Z. Returned: success |
|
An optional label to identify this entry. Returned: success |
|
The whitelisted value for the access control list. For example, to grant access to a client from an external IP (IPv4 or IPv6) address or subnet, use that address or subnet here. Returned: success |
|
Whether the instance should be assigned an IP address or not. Returned: success |
|
Whether the mysqld should default to ‘REQUIRE X509’ for users connecting over IP. Returned: success |
|
The version of instance settings. This is a required field for update method to make sure concurrent updates are handled properly. During update, use the most recent settingsVersion value for this instance and do not try to update this value. Returned: success |
|
The tier or machine type for this instance, for example db-n1-standard-1. For MySQL instances, this field determines whether the instance is Second Generation (recommended) or First Generation. Returned: success |
|
User-provided labels, represented as a dictionary where each label is a single key value pair. Returned: success |
|
The current serving state of the database instance. Returned: success |