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
    • 1Password
    • OpenVPN
    • Oracle Database
    • PostgreSQL
    • RabbitMQ
    • Rancher
    • RDP
    • Redis Cloud (Redislabs)
    • Amazon Redshift
    • Snowflake
    • SSH
    • Vertica Database
    • Web App
    • Windows Domain Controller
Powered by GitBook
On this page
  • Example Usage
  • Schema
  • Integration Config

Was this helpful?

Export as PDF
  1. INTEGRATION METADATA

Cloud Function Custom Integration

Cloud Function Custom Integration allows use GCP Cloud Function as a custom implementation for resource integration

Example Usage


cloudfunction-custom-integration-integration.tf
resource "apono_integration" "cloudfunction-custom-integration-integration" {
  name                     = "Cloud Function Custom Integration"
  type                     = "cloudfunction-custom-integration"
  connector_id             = "apono-connector-id"
  connected_resource_types = ["custom-cloud-function"]
  metadata = {
    access_details = "<Access Details>"
    custom_parameters = "<Custom Parameters>"
    project_id = "<Project ID>"
    region = "<Region>"
    function_name = "<Function Name>"
  }
}
cloudfunction-custom-integration-integration.tf
resource "apono_resource_integration" "cloudfunction-custom-integration-integration" {
  name                     = "Cloud Function Custom Integration"
  type                     = "cloudfunction-custom-integration"
  connector_id             = "apono-connector-id"
  connected_resource_types = ["custom-cloud-function"]
  integration_config = {
    access_details = "<Access Details>"
    custom_parameters = "<Custom Parameters>"
    project_id = "<Project ID>"
    region = "<Region>"
    function_name = "<Function Name>"
  }
}
cloudfunction-custom-integration-integration.json
{
    "cloudfunction-custom-integration-integration": {
        "name": "Cloud Function Custom Integration",
        "type": "cloudfunction-custom-integration",
        "connector_id": "apono-connector-id",
        "connected_resource_types": [
            "custom-cloud-function"
        ],
        "integration_config": {
            "access_details": "<Access Details>",
            "custom_parameters": "<Custom Parameters>",
            "project_id": "<Project ID>",
            "region": "<Region>",
            "function_name": "<Function Name>",
        }
    }
}

Schema


  • type cloudfunction-custom-integration

  • connected_resource_types List of resource types to sync.

Available resource types you can use
  • custom-cloud-function

Integration Config


  • access_details (Required | String) Access Details

  • custom_parameters (Required | String) Custom Parameters

  • project_id (Required | String) Project ID

  • region (Required | String) Region

  • function_name (Required | String) Function Name

PreviousAzure VM SSHNextF5 Network

Last updated 8 days ago

Was this helpful?