Changelogs | Brainboard

Stay up to date with our product development by checking out our public roadmap changelog. We regularly ship new features and integrations, so be sure to check in weekly, monthly or quarterly to see what's new and how it can benefit you and your business.
☁️ Cloud Provider
20 days ago

🌦️ Upgrade Terraform Providers

Cloud providers supported in Brainboard (AWS, Azure, OCI, GCP) were upgraded to its latest versions. 

Latest Terraform Providers' versions:  

AWS: VERSION 4.49.0
Azure: VERSION 3.38.0
OCI: VERSION 1.5.3
GCP: VERSION 4.48.0

For more information, check the official Terraform Providers registry.

☁️ Cloud Provider
about 1 month ago

≈ Variables in multi-region AWS diagram design

In Brainboard, this applied for all cloud providers supported (Azure, OCI, GCP, Scaleway)
You can now use variables in multi-region AWS diagram design :)

Terraform variables in Brainboard can be used to create a multi-region AWS diagram design in several ways:
  1. Use variables to define the regions you want to deploy your infrastructure in: By using Terraform variables; you can specify which regions you want to deploy your infrastructure in and make it easy to change or add regions in the future.
  2. Use variables to define the specific resources in each region: By using Terraform variables, you can specify the specific resources you want to deploy in each region. This allows you to create different resource configurations for different regions easily.
  3. Use variables to define the AMI ID: By using Terraform variables, you can specify the AMI ID (Amazon Machine Image) you want to use in each region. This allows you to use different AMIs for different regions.
  4. Use variables to define the subnets and availability zones: By using Terraform variables, you can specify the subnets and availability zones that you want to use in each region. This allows you to use different subnets and availability zones for different regions.
  5. Use variables to define the security group: Terraform variables can specify the security group you want to use in each region. This allows you to use different security groups for different regions.

Here is an example of how you can use Terraform variables to define a variable for the region:
variable "region" {
  default = "us-west-2"
}

You can use this variable in your resource definition like this:
resource "aws_instance" "example" {
  ami           = var.ami
  instance_type = "t2.micro"
  region        = var.region
}
☁️ Cloud Provider
3 months ago

☁️ OCI on Brainboard

Design, Deploy and Manage Oracle Cloud Infrastructure within Brainboard


We listened to your requests and just added OCI (Oracle Cloud Infrastructure) to Brainboard, your one-and-only IaC solution! 

For you, it means:
  • You can use Terraform to interact with Oracle Cloud Infrastructure resources
  • You can visually build your OCI cloud infrastructure and deploy it with ease
  • You can import any existing OCI-based repo, public and private onto Brainboard
  • You can convert all your OCI cloud infrastructures into reusable templates.
☁️ Cloud Provider
4 months ago

💣 Import from Microsoft Azure (public)

This summer, while many were enjoying their vacations, the development team at Brainboard was hard at work. They were focused on enhancing every aspect of the platform, and one of the most highly-anticipated features was the ability to import from Azure, now available to the public.

Introducing Import Azure

To celebrate this new feature, we are excited to offer you 50 free credits to import 50 Azure cloud resources and transform your Azure infrastructure into Terraform code and a live diagram. If you require additional credits, please don't hesitate to let us know. We are here to help you every step of the way.
☁️ Cloud Provider
8 months ago

🐞 AWS Gov regions alias

The issue being addressed is that in the providers.tf file, the AWS GovCloud regions were not included.

The development team has fixed this issue and now the GovCloud regions are listed with their own alias in the providers.tf file. This means that users can now use the appropriate alias to specify the GovCloud region they want to work with, instead of having to manually enter the region's endpoint.
AWS GovCloud (US-West) and AWS GovCloud (US-East) are regions that are specifically designed to host sensitive data and regulated workloads in the cloud, and they are isolated to the US Government's infrastructure. These regions provide a high level of security and compliance.

Examples of the regions include:
  • us-gov-east-1
  • us-gov-west-1

In summary, the bug fix addresses an issue where in the providers.tf file, the AWS GovCloud regions were not included. The development team has fixed this issue and now the GovCloud regions are listed with their own alias, which allows users to use the appropriate alias to specify the GovCloud region they want to work with, and it's more convenient, instead of having to manually enter the region's endpoint. AWS GovCloud regions are designed to host sensitive data and regulated workloads in the cloud, and they are isolated to the US Government's infrastructure.

Use AWS GovCloud resources with Brainboard.
☁️ Cloud Provider
9 months ago

🌐 Remote backend per architecture

Allow the user to change the remote backend setting at the architecture level.
ℹ️ For users/clients that want to manage multiple clients over multiple clouds and use a dedicated remote backend per client.

Remote Backend.png 205.83 KB
☁️ Cloud Provider
9 months ago

👁 Set Terraform provider’s setting

Allow you to add custom CP settings

Example of setting you can add in this block: 
Customize Terraform CP provider.mp4 3.36 MB


This feature is mainly for users that won’t deploy within Brainboard but already have their git and some TF provider settings.

Custom Terraform provider
☁️ Cloud Provider
10 months ago

📥 Terraform Reverse is open for early access!

Terraform Reverse is a feature that allows users to automatically generate Terraform diagrams and code from their existing resources on AWS and Azure, which is now available for early access. This means that users can now convert their existing resources on these cloud providers into actionable diagrams and Terraform code, which can be used to manage and maintain their infrastructure as code.

The feature is designed to save users time and money by allowing them to quickly and easily migrate their existing resources to Terraform. It takes less than 30 minutes to migrate 2500 resources instead of 6 months, which represents a significant time savings. Additionally, the feature can save users money by reducing the cost per resource migrated, which can add up to thousands of dollars at scale.

The feature also allows users to achieve a much faster time to infrastructure as code (IaC) and automation, with up to 100x faster time. This allows users to quickly and easily automate the management of their infrastructure, which can lead to increased efficiency and reduced human error.

Overall, Terraform Reverse is designed to help users save time and money by making it easy to migrate their existing resources to Brainboard and automate the management of their infrastructure. With this feature, users can take advantage of the benefits of IaC, such as increased efficiency and reduced human error, while minimizing the time and effort required to do so.
☁️ Cloud Provider
almost 2 years ago

Add Azure ☁️

Brainboard now supports Microsoft Azure!
Start creating your infrastructure with Azure now and deploy in an hour.
☁️ Cloud Provider
almost 2 years ago

Add GCP ☁️

Brainboard now supports Google Cloud Provider!
Start creating your infrastructure with GCP now and deploy in an hour.