LogoLogo
Metadata for Integration Config
Metadata for Integration Config
  • INTEGRATION METADATA
    • Amazon Account
    • AWS EC2 SSH
    • Elastic Kubernetes Service (EKS)
    • AWS Lambda Custom Integration
    • Amazon Organization
    • AWS RDS MySQL
    • AWS RDS PostgreSQL
    • Amazon RDS
    • Entra ID (Azure AD) Groups
    • Azure Kubernetes Service (AKS)
    • Azure Management Group
    • Azure MySQL
    • Azure PostgreSQL
    • Azure Subscription
    • Azure VM SSH
    • Cloud Function Custom Integration
    • F5 Network
    • Google AlloyDB
    • Google BigQuery
    • Google Cloud SQL - MySQL
    • Google Cloud SQL - PostgreSQL
    • Google Kubernetes Engine (GKE)
    • Google Organization
    • Google Project
    • Github
    • JumpCloud
    • Kubernetes Proxy
    • Kubernetes
    • LDAP Group
    • MariaDB
    • Mongo Atlas Portal
    • MongoDB Atlas
    • MongoDB
    • Microsoft SQL Server
    • MySQL
    • Okta Group
    • OneLogin Group
    • OpenVPN
    • Oracle Database
    • PostgreSQL
    • Rancher
    • RDP
    • Redis Cloud (Redislabs)
    • Amazon Redshift
    • Snowflake
    • SSH
    • Vertica Database
    • Web App
    • Windows Domain Controller
Powered by GitBook
On this page
  • Example Terraform Resource Usage
  • Schema
  • Metadata

Was this helpful?

Export as PDF
  1. INTEGRATION METADATA

Google Cloud SQL - PostgreSQL

An open-source relational database management system emphasizing extensibility and SQL compliance.

Example Terraform Resource Usage


resource "apono_integration" "gcp-cloud-sql-postgresql-integration" {
  name                     = "Google Cloud SQL - PostgreSQL"
  type                     = "gcp-cloud-sql-postgresql"
  connector_id             = "apono-connector-id"
  connected_resource_types = ["resource-type-1", "resource-type-2"]
  metadata = {
    auth_type = "<Auth Type>"
    gcp_project_id = "<Project ID>"
    gcp_region = "<Region>"
    gcp_instance_id = "<Instance ID>"
    gcp_instance_id_user_override = "<Instance ID User Override>"
    dbname = "<Database Name>"
    sslmode = "<SSL Mode>"
    credentials_rotation_period_in_days = "<Credentials rotation period (in days)>"
    credentials_cleanup_period_in_days = "<User cleanup after access is revoked (in days)>"
  }
  gcp_secret = {
    project    = "project_template_value"
    secret_id  = "gcp_secret_id_template_value"
  }
}

Schema


  • type gcp-cloud-sql-postgresql

  • connected_resource_types List of resource types to sync. The following are the available resource type/s you can use:

    • gcp-cloud-sql-postgresql-database

    • gcp-cloud-sql-postgresql-table

    • gcp-cloud-sql-postgresql-role

Metadata

  • auth_type (Required | String) Auth Type

    • Possible values: gcp-iam-auth, user-password

  • gcp_project_id (Required | String) Project ID

  • gcp_region (Required | String) Region

  • gcp_instance_id (Required | String) Instance ID

  • gcp_instance_id_user_override (Optional | String) Instance ID User Override

  • dbname (Required | String) Database Name

    • Default value: postgres

  • sslmode (Optional | String) SSL Mode

    • Possible values: disable, allow, prefer, require, verify-ca, verify-full

  • credentials_rotation_period_in_days (Optional | String) Credentials rotation period (in days)

  • credentials_cleanup_period_in_days (Optional | String) User cleanup after access is revoked (in days)

PreviousGoogle Cloud SQL - MySQLNextGoogle Kubernetes Engine (GKE)

Last updated 3 days ago

Was this helpful?