Brainboard Cloud | Changelog

Explore our Terraform development updates on our public roadmap changelog. Discover new features and integrations regularly. Check in weekly, monthly, or quarterly to see the latest enhancements benefiting your business.
🔥 Product Launches
29 days ago

Brainboard set for Enterprise Workload

Our goal is to make Brainboard the ideal solution for Enterprise workload and we are implementing more integrations and workflows in this direction.

Fine-grained RBAC at the design level

You can now proactively control the cloud resources that are available to your users by enabling / disabling what they can see and use from the leftbar.

Brainboard Enterprise.png 1.27 MB

Main use-cases:
  • →You want to restrict access to a certain types of resources, like networking and security, and make sure that users only see and use the resources they need. No more.
  • →You want your teams to only use Terraform modules and none of the vanilla resources as part of your standardization plan.

Brainboard API

To extend the use of Brainboard and integrate more with Enterprise workloads, we made our API available. This helps you orchestrate workflows and executions from an outside source, like ServiceNow or Jira.

💡 Usage example: Give your internal users a portal where they can just fill few information, and you use the API of Brainboard to clone their use-case from the template catalog into a specific project and environment, populate the variables and trigger the CI/CD pipelines for deployment.

Private self-hosted runner

You can now host Brainboard private runner within your infrastructure to make sure the execution happens in your environment and your sensitive information and secrets stay within your boundaries.

Service catalog — producer consumer

This feature allows you to capture all the infrastructure patterns to create an internal service catalog. This helps teams to not reinvent the wheel and consume cloud architectures that have been approved from security and cost perspective while allowing them to work autonomously.

Private registry support

This is our greatest, last but not least, integration. You can bring your private Terraform registry into Brainboard, it is now natively supported.

Davids video-4k.mp4 1.8 MB

To make it even easier and most importantly convenient for your usage, you have different level of token to connect your registry. You can either use a personal token or group / organization one, so your users don’t worry about the integration and just use the approved modules you make available for them.
🔥 Product Launches
about 2 months ago

🔥 Terraform State Management

To give you the safest way possible to interact with your tfstate, we just released an amazing feature that allows you to safely: 
  • See your tfstate and fetch the latest version from your remote backend (if you are not using the default one)
  • Manipulate it to import / add or remove resources
  • List the resources inside
  • Move it
  • Execute Terraform actions on it.
This is visible and available in a new tab called “Settings” to separate it from the CI/CD page.

🔥 Product Launches
4 months ago

🚀 New Product Launch

We are preparing a revolutionary product to visualize your terraform code. We are selecting a few users for the private alpha.

What to expect:

  • Allow you to instantly visualize your terraform code with high quality precision, instead of rigorous and laborious manual creation.
  • Full support of terraform modules.
  • In the first version, only AWS will be supported.
  • Available as a CLI that can be executed in your CI/CD to generate a picture of your infrastructure.
🔥 Product Launches
5 months ago

💥 OpenTofu on Brainboard

We're thrilled to introduce a game-changing addition to Brainboard - OpenTofu! 🎉

OpenTofu, Terraform’s most promising fork, is an #opensource and drop-in replacement to HashiCorp's Terraform. They recently shipped their 1st stable version 1.6.0.

Here’s how to use OpenTofu on Brainboard:
1️⃣ In the canvas, design your cloud architecture
2️⃣ In the deploy settings (CI/CD tab), set OpenTofu as binary
3️⃣ Run any one action like validate or plan

OpenTofu on Brainboard

Give OpenTofu a spin here!
Stay tuned for further development.
🔥 Product Launches
7 months ago

🔥 Feature Requests 🔥

✨ Brainboard AI: 

We're thrilled to announce that Bob, our AI-driven cloud kickstarter, will be in beta access by January 1st 2024! Request Access.

🧑‍💻 Edit Existing Resources: 

In this alpha version, you can edit the terraform code of existing resources.
This improvement is the first step towards giving you the best of both words, the power of the design and the accuracy of code. Request Access.

🌧️ Import from AWS

We already fully support Import from Azure, and now, Import from AWS is available in a beta version only for Enterprise clients. Reach out to us to discuss your use case and how we can help you migrate to IaC & Brainboard. Request Access.
🔥 Product Launches
7 months ago

🌧️ Import AWS

We already support Import Azure, and now, Import AWS is available only for few Enterprise clients.
Please contact the Sales team if you want to discuss your use case and migrate your infrastructure into Brainboard.

Import AWS
🔥 Product Launches
8 months ago

👩🏻‍💻 Introduction of the Bi-directional Alpha Feature

In this alpha version, you can edit existing resources only. (cf. more information)

Animated GIF Maker.gif 2.76 KB

edit terraform code

ezgif video.gif 1.41 MB

You still have to drag & drop new resources but then either you update them via the idcard or via the code. Every edits you do are reflected into the diagram 👀
  1. Modify the value of an existing attribute for a specific resource, variable, or block within the Terraform code.
  2. Introduce new attributes or blocks for configurations such as a resource, relationship, Terraform module filename, or a distinct architectural design.
  3. Remove unnecessary attributes or blocks; the diagram will automatically update to reflect these changes.
🔥 Product Launches
over 1 year ago

Welcome to the era of the CI/CD Workflow Designer, your all-in-one CICD engine!

You can: 

  • Visually design and orchestrate your deployment workflows without a single line of code.
  • Connect your automation ecosystem with OPA, Infracost, Checkov, or Terrascan…
  • Centralize your custom automation strategies and remote-run deployments.
  • Execute, optimize and manage workflows for successful outputs.
  • One of the biggest added values in terms of deployment is that Brainboard manages the upgrades and maintenance of the supported plugins: Infracost, OPA…

Brainboard’s CICD workflow designer is out now. Discover it for free →

PS. Please note that we're improving constantly the feature. Honest feedback would be grateful.
🔥 Product Launches
over 1 year ago

🗂 Import Terraform .tfvars* files

* tfvars files are Terraform configuration files that store variables for a Terraform configuration. They typically have the file extension .tfvars and are used to set values for variables that are used in Terraform configuration files. These files allow you to store sensitive information like credentials and other sensitive data, which you can use in your Terraform configuration, but without having to hard-code them in your .tf files.
This bug fix likely addresses an issue where users were unable to set values for variables when they were importing resources into Brainboard. An import allows a user to take an existing resource that was not created by Terraform and bring it under Brainboard management. However, if there is a bug that prevents users from setting variable values during an import, it would make it difficult for them to properly manage these resources.

The bug fix likely addressed this issue by allowing users to provide variable values during an import, allowing them to properly manage the imported resources. This would enable the users to import resources, and also set values for the variables that they want to use to manage these resources.

Discover Brainboard

🔥 Product Launches
over 1 year 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.
🔥 Product Launches
almost 2 years ago

👥 Multiple git credentials

At Brainboard, we've worked hard to take your experience with the Cloud to the next level, especially while managing Git credentials in teams.

We've enabled you to:
  • As an individual contributor, you can add personal git tokens for any supported git provider - Azure DevOps, Gitlab, Bitbucket - and specify the scope of the creds and have visibility on where they are used.
  • As the owner of the organization, you can add Github app integration and users perform git actions based on their authorization on Github.
What do you need to do:
  • The Git credentials of your organizations are assigned to the owner of the organization. So you need to add your personal token in order to do pull requests. 
  • If you use GitHub, there is nothing to do. Your pull requests work as before. 
  • Pull requests: Choose the git provider to use from the supported ones - Azure DevOps, Gitlab, Bitbucket, GitHub, and add the description, project, folder, and base branch within the service.
  • Modules: You can choose which git credentials you want to use to import your private modules and use them.
  • Generate your diagram from the terraform code: Choose the git credentials you want to use and import your existing terraform code.
Both categories, git apps and personal tokens, are available on the 'Account' configurations, here:
This new set-up capability enables the seamless performance of tasks without switching between accounts and re-authenticating accesses, and so work independently and well.

🔥 Product Launches
about 2 years 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.
🔥 Product Launches
over 2 years ago

🔗 ☁️ Import Terraform V02

This feature is a tool that allows users to import Terraform, a tool used for infrastructure as code, and manage it visually. We've been collecting feedback from users since its release last month and has been making improvements and releasing new versions daily. 

Reverse Terraform is a feature of Brainboard that allows users to automatically generate Terraform diagrams and code from an existing Terraform file, a public or private repository, and connect to their cloud provider's credentials. This feature enables users to create visual representations of their infrastructure and quickly understand the relationships between resources, as well as generate Terraform code for those resources, making it easier to manage and maintain their infrastructure. Additionally, by connecting to cloud provider credentials, Brainboard can also pull in information about existing resources and use that to generate the Terraform code, allowing users to easily import their existing infrastructure into Terraform.

The new versions include features such as: 
  • Private Repositories (Only GitHub): This fix allows users to connect to their private GitHub repositories and import their Terraform code. This is useful for users who want to keep their infrastructure code private and only accessible to authorized users.
  • Supports count, timeouts, depends_on (add connector with the dedicated This fix enables the tool to support count, timeouts, and depends_on Terraform resources, which are used to create multiple instances of a resource, set timeouts for resources, and specify dependencies between resources. The tool also allows users to add connectors with the dedicated
  • Supports terraform functions (like format, substr, ...), string interpolation (like “aaa$[var.test]”): This fix enables the tool to support Terraform functions, such as format and substr, and string interpolation. Terraform functions are used to perform various operations on strings and variables, while string interpolation allows users to include variables within strings.
  • Some resource attributes not parsed: This refers to an issue where some resource attributes were not being parsed correctly by the tool. This fix addresses this issue, ensuring that all resource attributes are parsed correctly.
  • Create module idcard on the fly: This fix allows users to create module idcards on the fly. A module idcard is a summary of a module's inputs, outputs, and resources. This allows users to quickly understand the purpose and structure of a module without having to examine its code.
  • Import code with module fails: bad source, no version: This refers to an issue where importing code with modules would fail if the source or version was not specified correctly. This fix addresses this issue, allowing users to import code with modules correctly.
  • Git root/base repo URL doesn't work: This refers to an issue where the git root or base repo URL was not working correctly. This fix addresses this issue, ensuring that the git root/base repo URL works correctly.
  • Support EOF in resource attribute: This fix enables the tool to support EOF in resource attribute. EOF, short for End-of-file, is a control code used to indicate the end of a file or stream. This fix allows the tool to correctly handle EOF in the resource attribute.

Migrate your cloud infrastructure on Brainboard for a better process standardization. 

import your tf code .gif 1.69 MB
Powered by FeedBear