Brainboard's documentation
Go to the app ↗
  • Welcome
  • Getting started
    • Fast track
    • Start with a template
    • Start with AI
    • Use cases videos
    • Brainboard philosophy
  • Cloud design
    • Left bar
      • Cloud resources
      • Input & output
    • Design area
      • Node
      • ID card
      • Connectors
      • Versioning
      • Graphical options
    • One action
    • Code Edition
  • Data
    • Data structure
      • Project
      • Environment
      • Cloud architecture
        • Terraform files
        • Readme file
        • Architecture Synchronization
        • Remote backend
      • Template
    • Cloud providers
      • Supported cloud providers
      • Customize provider configuration
      • Unsupported cloud providers
    • Terraform / OpenTofu
      • Modules
        • Module
        • Import modules
        • Manage module
        • Terraform registry credentials
        • Use modules
    • Disaster recovery
  • Automation
    • CI/CD engine
    • Supported plugins
      • Terraform
      • Security
        • Trivy
        • Tfsec
        • Terrascan
        • OPA
        • Checkov
      • Infracost
      • Notifications
        • Email
        • Slack
        • Microsoft Teams
      • Webhooks
    • Pipelines
    • Workflow templates
    • Drift detection
      • Types of drift
      • Remediation
    • Self-Hosted Runner
      • Deploy runner with Kubernetes
      • Deploy runner with docker-compose
  • Settings
    • Overview
    • Authentication
      • Login into Brainboard
      • Single sign-on (SSO)
    • Account management
    • Organization
    • Members
    • Teams
    • Roles & Permissions (RBAC)
      • Level of access
      • Organization RBAC
      • Project RBAC
    • Integrations
      • Git configuration
        • GitHub
        • Azure DevOps (ADO)
        • Bitbucket
        • GitLab
        • How to use
      • Cloud providers
        • AWS
        • Azure
        • GCP
        • OCI
  • Security
    • Data managed by Brainboard
    • SOC 2 Type II
    • Role Based Access Control
  • Help & FAQ
    • Shortcuts
    • FAQ
    • Migration
      • Import from cloud provider
    • Support
    • Glossary
  • Changelog
Powered by GitBook
On this page
  • Description
  • Palo Alto Terraform provider
  • Cloud Provider Configuration

Was this helpful?

Edit on GitHub
  1. Data
  2. Cloud providers

Unsupported cloud providers

Description

Terraform supports a wide range of providers, including popular cloud providers, infrastructure providers, and SaaS providers.

They can be categorized as :

  • Official providers are owned and maintained by HashiCorp

  • Partner providers are written, maintained, validated and published by third-party companies against their own APIs.

  • Community providers are published to the Terraform Registry by individual maintainers, groups of maintainers, or other members of the Terraform community.

Besides the providers that are supported by Brainboard (Azure, AWS, GCP, OCI, Scaleway), you can use all the other providers by following these steps:

  1. Add the configuration for the cloud providers on the cloud provider configuration.

  2. Add a new resource for that provider by using custom resources.

To illustrate it, let's consider Palo Alto as a Terraform provider that is not supported by Brainboard and see how we can use it.

Palo Alto Terraform provider

The Palo Alto Networks Terraform provider is a plugin for Terraform that allows you to manage Palo Alto Networks resources, such as firewalls, in Terraform. The provider provides a set of Terraform resources that map to corresponding Palo Alto Networks resources, allowing you to manage your network infrastructure as code.

Cloud Provider Configuration

To configure the Palo Alto Networks provider, you need to follow these steps:

Configure the provider

Open the custom provider configuration by clicking on the gear visible in the cloud providers selection.

In the custom provider's block, you'll need to configure the Palo Alto Networks provider by specifying the required parameters. This may include the API key or other credentials to connect to the Palo Alto Networks platform. A sample provider configuration block could look like this:

provider "paloalto" {
  api_key = "<your-api-key>"
}

Add a resource

Once the provider is configured, you can add a resource in Brainboard. For example, you could create a firewall rule in Palo Alto Networks like this:

  • At the bottom of the Leftbar, you can find the custom resources. This is a block that you can add terraform resources that are not supported yet by Brainboard.

  • Drag and drop the custom resource, open its configuration and complete the information

    • Type of the block: Add either resource if you want to provision a new resource, or data.

    • Type of the new resource: Add the type of the new resource from the cloud provider. In this example, is paloalto_security_rule.

    • Resource name: Add a name for your new resource.

    • Terraform code of the resource: Add the resource code and configuration into this field.

    • Icon: Add a custom icon by clicking on the icon at the top of the configuration panel

  • After finishing these steps, you can use the resource as other supported resources in Brainboard and test it by running the terraform plan/apply command to create or update the resources in the Palo Alto Networks platform.

PreviousCustomize provider configurationNextTerraform / OpenTofu

Last updated 8 months ago

Was this helpful?

Providers block
Custom resource
Palo Alto resource