# 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.

![Providers block](/files/pGIj6xcyQHSPexB8CsGf)

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:

```hcl
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.

  ![Custom resource](/files/c5KR9yWyv96Vf3ZEzNYb)
* Drag and drop the custom resource, open its configuration and complete the information&#x20;

  ![Palo Alto resource](/files/71TfM0PzREyI6roCfBjb)

  * **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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.brainboard.co/data/cloud-providers/unsupported-cloud-providers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.