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.
🎨 Design area
about 4 hours ago

Brainboard Feature Changelog - Week #4 - January 2023

We're excited to share with you the latest updates and improvements to our platform. Here's a summary of what we've been working on this week:

🐞 FIXED

We've resolved reported issues that were causing occasional crashes when, for example:
Pull Request by Brainboard
  1. Specify a different brand when doing a pull request:
    • We now allow you to specify a different branch in the base branch field in the pull request modal, when creating a pull request. This means that you are able to select which branch they want to merge their changes into, rather than being restricted to a specific branch such as “main”. This feature can be useful for organizations that use multiple branches for development and testing, as it allows developers to easily collaborate on code changes and merge them into the appropriate branch for deployment. Additionally, it can help to maintain the versioning and history of the Terraform codebase.
  2. GCP VPC and Subnet: 
    • They were not containers*. Now, they are… 
    • Containers* in the cloud refers to the use of containerization technology to deploy and manage applications in a cloud computing environment. Containers are a lightweight and portable way to package and deploy applications, and they can be run on a variety of platforms, including Google Cloud. Containers are isolated from one another, which helps to increase security and reduce the chances of conflicts between different applications. 
    • Google Cloud offers a service called Google Kubernetes Engine (GKE) which allows you to easily deploy, scale, and manage containerized applications on the cloud.
    • Google Compute Network (GCN) is a virtual network that allows you to create and manage a network topology for your Google Cloud resources. It allows you to create subnets, firewall rules, and routes to control how your resources communicate with each other and with the internet.
    • Google Compute Subnetwork (GCSN) is a subnet within a GCN that allows you to segment your network into smaller, more manageable pieces. It also enables you to control the IP ranges for resources in a subnet, and apply firewall rules and routes to specific subnets.
  3. Variable type not saved:
    • Problem: This bug fix addresses an issue where a new variable is not correctly saving the type information during the creation or modification process. This can cause problems with the functionality of the application, as the type of variable is important for determining how the application should handle and interact with the variable's value.
    • Solution: The fix involves updating the Terraform code that is responsible for handling the creation and modification of variables to properly save the type information. This could involve checking for missing or incorrect type information, and adding code to handle this properly. Additionally, it also involves testing the updated Terraform code to ensure that the bug is resolved and that the new variables are being created and modified correctly with the correct type information. 
  4. Custom group TF file broken:
    • Problem: The bug fix addresses an issue with the functionality that retrieves custom group files in Terraform. The bug is related to the fact that when a group starts with 'f' or 't' the retrieval of the custom group file is broken. The issue with the Terraform configuration for the “test” group, as the test.tf file should contain the necessary information for provisioning and managing the infrastructure for that group, but it is empty. 
    • Solution: Create an architecture or a blueprint of the infrastructure using Terraform. Add 3–4 nodes on the design canvas, which are servers or machines that make up the cloud infrastructure. Change the group of 2 of the nodes to “test” group. Now, retrieve the test.tf file, which should contain the Terraform configuration for the “test” group.
  5. Scroll through a big output:
    • Problem: The bug fix addresses an issue with the performance of scrolling through the output of the “plan” in Terraform. The bug is causing the scrolling to be slow and unresponsive, with a delay of 2–3 seconds before the update or the next lines are displayed.
    • Solution: We optimized the code that handles the output display and scrolling by reducing the number of updates and unnecessary calculations. We always make sure the data is being loaded and processed efficiently.
  6. Import Multiple strings:
    • Problem: The bug fix addresses an issue with the way Brainboard import Terraform code that contains "<<EOF" and "EOF" for a field. The bug causes these characters to be changed into strings which causes issues in the interpretation of the code.
    • Solution: Update the import code to properly handle these characters. We make sure the code that reads and interpret the imported Terraform code is able to handle these characters correctly.
  7. Feedback survey:
    • Problem: We noticed that the feedback form brought aggressive prompts to you, builders and cloud architects. 
    • Solution: We've disabled it for now. Please continue to contribute to the Slack community and contact us if any improvements need to be fixed. We generally respond within 6h. 
  8. Editing node title:
    Cloud Architecture Design canvas by Brainboard
    • Problem: The bug fixes you addresses an issue with the way the editing of the title of a node behaves in Brainboard's canvas. The bug causes the title of the selected node to change when editing the title of a different node that is not selected.
    • Solution: We added a check to verify that the correct node is being edited, or by making sure the system is keeping track of the correct selected node.
We apologize for any inconvenience this may have caused, and thank you for bringing it to our attention.
Please note that the above issues have been fixed in the latest version of Brainboard and should no longer occur. If you continue to experience any issues, please reach out to our support team on our Public Slack Channel.

🧼 IMPROVED

We've made some performance enhancements to the:


  1. CI/CD Engine: We've just introduced a feature for approval tasks, which allows users to request and receive approval before deploying code changes to a production environment. This can be useful for ensuring that code changes have been reviewed and tested properly before they are deployed to a live environment, and can help to prevent errors or issues that could negatively impact the performance or functionality of the system.
  2. Import: We continue to improve the import feature. This week, we've focused on database use case. Now, you can import schema and documentation. A schema is the structure of the database and the rules on how the data should be organized, while a document is a single unit of data stored within the database.
  3. Deleting cloud architectures: When soft-deleting cloud architectures, we now soft delete all related objects including workflow(s), pipelines, jobs, deployments, git integrations, and terraform settings.
This should result in faster load times and a smoother user experience.

As always, we value your feedback and suggestions. If you have any thoughts or ideas on how we can improve Brainboard, please don't hesitate to reach out to our support team.

📆 Replay: Understand CI/CD strategies & Best Practices 


You can now watch last Tuesday's webinar on the details and implications of what CI/CD means for the cloud infrastructure. This is a short preview of what you will learn in less than 70 minutes: 
🎨 Design area
7 days ago

Brainboard Feature Changelog - Week #3 - January 2023

We're excited to share with you the latest updates and improvements to our platform. Here's a summary of what we've been working on this week:

🐞 FIXED

We've resolved reported issues that were causing occasional crashes when, for example:

Modules' catalog in Brainboard.


  1. Storage Container already exists issue:
    • Problem: When creating a new Storage Container in Brainboard, if the container already exists in AWS or Azure, the application would fail.
    • Solution: We have implemented a check that verifies if the container already exists in the specified cloud provider before attempting to create it. If the container already exists, Brainboard will no longer fail and will instead display a message indicating that the container already exists.
  2. Git Personal Token Editing Error:
    • Problem: When editing only one field in the Git Personal Token, an error occurred and the changes were not saved.
    • Solution: We have identified the problem and fixed the issue with the Git Personal Token editing process. Users should now be able to edit any field in the token without encountering errors.
  3. Terraform Block Removal:
    • Problem: When importing Terraform files, such as backend.tf that contains a Terraform block and many providers block, the Terraform block was automatically removed.
    • Solution: We have identified the problem and fixed the issue with the Terraform block removal during import. The Terraform block should now be retained and not removed during the import process.
  4. Map variable syntax issue:
    • Problem: When importing a Terraform file that contains a map as the type of variable and the values are defined in terraform.tfvars, the values were changed and replaced with an invalid Terraform syntax, causing the plan to fail,
    • Solution: We have identified the problem and fixed the issue with the map variable syntax. The values should now be imported correctly and retain their original syntax.
  5. Validation Block Import:
    • Problem: When importing from Git or files, for example, a Terraform code that contains a validation block, the variables validation block was not imported in Brainboard.
    • Solution: We have identified the problem and fixed the issue with the validation block import. The variables validation block should now be imported correctly and be visible in Brainboard.
  6. Terraform Variables Modal:
    • Problem: The Terraform variable modal was changing every time it was opened or when doing a pull request. This caused confusion and made it difficult to track changes.
    • Solution: We have made changes to the Terraform variable modal, so it will no longer change every time it is opened or when doing a pull request. This will make it easier to track changes and manage variables.
  7. Default Terraform Code File:
    • Problem: The default Terraform code file was main.tf, but it was causing confusion when working on a different resource file.
    • Solution: We have changed the default Terraform code file to be the resource file that the user is currently working on. This will make it easier to manage multiple resource files and keep track of changes.
We apologize for any inconvenience this may have caused, and thank you for bringing it to our attention.
Please note that the above issues have been fixed in the latest version of Brainboard and should no longer occur. If you continue to experience any issues, please reach out to our support team on our Public Slack Channel.

🧼 IMPROVED

  1. Terraform Code Generation: We have made significant improvements to its Terraform code automatic generation process, making it 2x faster and more reliable. By optimizing the code generation algorithms, Brainboard has made it possible to generate Terraform code from diagrams in a fraction of the time it used to take. Additionally, the code generated is more reliable and maintainable for the long term. The generated code is now more readable and easier to understand, making it simple to read changes and updates. The new generation process also includes a new error checking feature, which identifies and corrects errors before the code is generated, ensuring that the generated code is error-free. Overall, these improvements make Brainboard's Terraform code generation process one of the best in the industry, providing users with a fast, reliable, and maintainable solution.
  2. CI/CD Plugins: We have added more available arguments and options for CI/CD plugins. This will give users more flexibility and control when integrating with their CI/CD pipeline.
This should result in faster load times and a smoother user experience.

As always, we value your feedback and suggestions. If you have any thoughts or ideas on how we can improve Brainboard, please don't hesitate to reach out to our support team.

📆 Thursday, January 24th, 2022



Don't forget our live webinar on the details and implications of what CI/CD means for the cloud infrastructure:
  • The current state of CI/CD solutions and how they work
  • The challenges associated with it and how they impact your process
  • What are the best practices that apply to the infrastructure automation
  • What changes are needed to have a successful implementation
  • The most important part: what is expected from a CI/CD solution that is cloud infrastructure specific
🎨 Design area
12 days ago

⧮ Improve PR/MR* creation flow with clear error messages!

*
PR = Pull Requests
MR = Merge Requests

Brainboard's tech team has significantly improved the error messaging experience when performing pull or merge requests.

To accomplish this, we have changed the backend to provide more detailed and informative error messages. These error messages are now displayed directly on the front end, making it easy for you to understand and resolve any issues that may arise. We have also made improvements to the modal's User Experience (UX) to make it more intuitive and user-friendly. 

These enhancements will make it easier for you to manage and troubleshoot your code changes.


About

Merge requests (MRs) & pull requests (PR) in a version control system (VCS) like Git can save your cloud infrastructure project by allowing you to:

  1. Collaborate effectively with team members: PR/MR provide a way for team members to propose changes to the infrastructure codebase and review and discuss them with other team members before merging them into the main branch. This allows for better collaboration and communication within the team.
  2. Implement code review and testing processes: PR/MR provides a way to implement a code review process, where other team members review changes to the infrastructure codebase before being merged. This can help identify and fix bugs and issues before they are deployed to production.
  3. Track changes to the infrastructure codebase: PR/MR provides a way to track changes to the codebase, including who made the change and why making it easier to understand how the infrastructure has evolved.
  4. Rollback changes: PR/MR provides a way to roll back changes to the infrastructure codebase if something goes wrong. This can be done by reverting the merge commit or using version control tools like Git to revert specific changes.
  5. Isolate changes: PR/MR provides a way to isolate changes, meaning that changes are committed and tested in a separate branch before merging into the main branch. This allows for keeping the main branch stable and ready to deploy at all times.
  6. Implement automated testing and integration: PR/MR provides a way to implement an automated testing and integration process. This can be done by integrating the VCS with a continuous integration and deployment tool, which can run automated tests and deploy changes to different environments.

One step forward binary way of working the infrastructure on Brainboard
🎨 Design area
12 days ago

🔥 Id card is constantly improving

The ID card in Brainboard is a feature that enables users to easily configure cloud resources by dragging and dropping them onto the design canvas. These resources are not just visual representations but are actual, actionable resources that can be configured and deployed to the cloud. One step forward in breaking down the barriers between low-code and code-based approaches to cloud infrastructure management.

With the ID card, Brainboard is pushing the boundaries of visualizing cloud infrastructure to help you understand the bigger picture of your projects, environments, cloud architecture, and workflows. This makes it easier for users to manage your cloud resources and have a clear infrastructure overview. This can also help users to identify patterns, dependencies, and potential issues, making it easier to optimize your infrastructure.

Here at Brainboard, we constantly spot errors and improvements and focus on tackling them first. 
  • One of the improvements is that it eliminates missing fields when configuring specific cloud resources. You no longer have to worry about missing important information when setting up your cloud infrastructure. 
  • The ID card allows for multi-block everywhere, allowing for better customization options. This can be achieved by using hardcode, a powerful tool for making changes to the infrastructure. 

Overall, these improvements make it easier for you to configure and manage your cloud resources with Brainboard.
🎨 Design area
19 days ago

↕ Connect multiple resources directly from the idcard

Use an attribute of a resource in the id card of another resource and connect resources — one step further to low coding your cloud infrastructures.

In Brainboard, you can connect multiple resources by using resource references. This can be done in several ways:
  1. Using the "depends_on" argument in resource blocks allows you to specify that a resource depends on another resource and must be created after it.
  2. Using the "${resource.name.attribute}" syntax allows you to reference the attributes of one resource in the configuration of another resource.
  3. Using the "data" blocks to retrieve information from external resources allows you to retrieve information from existing resources and use it to configure new resources.
  4. Terraform modules allow you to group resources and reuse them across multiple configurations. This is a way to organize your resources and share them with others.
  5. Using Terraform's variables: Terraform variables can store resource information and reference it in multiple places in your configuration.

It's important to note that connecting multiple resources depends on the resources themselves and the cloud provider you are using. It is recommended to check the resources and provider documentation to get the best practices.
🎨 Design area
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
}
🎨 Design area
about 1 month ago

🔎 ID card* search now returns nested fields (inside block)

Improvement to the ID card search functionality in a system. Specifically, the improvement allows for searching nested fields within an ID card.
*The ID cards would represent different cloud resources, such as virtual machines, load balancers, and storage volumes. By dragging and dropping these ID cards onto a canvas, users could quickly and easily design their desired cloud infrastructure.

Once the diagram is designed, it would also be actionable, meaning that the user could deploy their cloud infrastructure with a single click. Brainboard would then automatically provision and configure the necessary resources based on the ID cards that were used in the design.

Brainboard greatly simplify the process of designing and deploying cloud infrastructure, as it would provide users with a visual, intuitive way to work with the resources. Additionally, the use of ID cards could also enable users to easily share and reuse their cloud infrastructure designs with others.

Before

The previous version of the ID card search only returned the matches from the simple fields, but now the search has been updated to return matches even from the nested/block fields, which allows the user to find the ID card with all the information they need.

Test it for yourself on Brainboard!

🎨 Design area
4 months 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

🎨 Design area
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.
🎨 Design area
4 months ago

✏️ Design to Code

The transition between design and code has been made easier, more responsive and more flexible. Cloud resources can be opened and closed to focus on designing the architecture diagram and Terraform code can be opened and closed to focus on configuration. This new feature was recently developed by our front-end experts and I was impressed with it after trying it out. It's truly amazing and I wanted to share it in this month's newsletter. Try it out for yourself!


Discover the new Design to Code area on Brainboard.
🎨 Design area
4 months ago

🚀 Code to Deploy

Brainboard have made significant improvements to the process of configuring cloud resources, specifically in regard to the identification and management of each resource. This is an essential task when building an architecture diagram, and we recognized the need for a more streamlined and efficient approach.

We have completely redesigned the concept of configuring a cloud resource, with a focus on simplifying the process and reducing the number of steps required. This has been achieved through the integration of more advanced automation techniques and the use of more intuitive user interfaces.

In addition to this, we have also made improvements to the design to code feature, which allows for a more seamless transition between designing the architecture diagram and configuring the relevant code. The combination of these two features results in a much smoother overall experience for the user.

I have personally tested these new features and can confidently say that it is a significant improvement from the previous version. I highly recommend giving it a try for yourself and see the difference.

Design to Code within the hour on Brainboard.
id-card.gif 716.25 KB
🎨 Design area
4 months ago

🖼 Use your own icon for any resource

This feature release pertains to the new id card that has been introduced in the Brainboard cloud management solution. With this new feature, users are now able to directly edit the icon of any resource when configuring it.

To do this, the user simply needs to hover their cursor over the existing icon and a prompt will appear, allowing them to upload a custom icon. This feature allows for a greater degree of customization and organization when building and managing architecture diagrams within Brainboard. Additionally, it gives users the ability to easily identify resources in diagrams by custom icons.

Start configuring your cloud resources with Brainboard.

Edit the resource's icon from the id card directly.
🎨 Design area
4 months ago

🪄 Import from files improved

This feature release pertains to the import feature in the Brainboard cloud management solution. The development team has been working on improving the user experience and the output of this feature.

A new and improved version of the import feature has just been released. With this new version, users are now able to start configuring their cloud resources while they are dragging and dropping them onto their architecture diagram. This means that users no longer have to complete the configuration process after the resources have been imported, they can now do it in real-time as they are adding resources to the diagram. This allows for a more efficient and streamlined workflow, and can save users valuable time.

The team is encouraging users to try out this new feature and provide feedback on their experience with it. This will help the team continue to improve the product and provide the best experience for the users.

 
Import your Terraform files on Brainboard.
Import from terraform file(s)
🎨 Design area
5 months ago

🌈 UX redesign - idcard

This feature release pertains to the redesign of the id card in the Brainboard cloud management solution. The development team has completely rethought the concept of the id card to improve productivity and readability for the users.

The new id card has been redesigned with the goal of providing a more efficient and streamlined workflow when configuring cloud resources. One of the key changes is that users can now start configuring their cloud resources while they are dragging and dropping them onto their architecture diagram. This eliminates the need to switch back and forth between configuring resources and adding them to the diagram, allowing for a more efficient workflow.

In addition to this, the new id card has been optimized for smoother readability. This includes improvements to the layout, typography, and color scheme. The new design is intended to make it easier for users to quickly and easily identify the relevant information for each resource, which can save valuable time when building and managing architecture diagrams.

The new id card also includes advanced automation techniques and more intuitive user interfaces which makes the overall process of configuring cloud resources faster and more user-friendly.


Overall, the redesign of the id card is aimed at improving the productivity and readability of the Brainboard cloud management solution, and providing a better experience for the users.

Start configuring your first resources on Brainboard.

id-card.png 107.04 KB
🎨 Design area
7 months ago

☁️ GCP tags broken

The feature being mentioned in this statement pertains to the handling of tags in the Google Cloud Provider (GCP) for Terraform, a tool for building, changing, and versioning infrastructure. The issue being addressed is that GCP Terraform tags were not working correctly, resulting in broken functionality.

The development team has fixed this issue and now GCP Terraform tags are correctly handled, meaning that users should no longer experience issues with broken functionality.

In Terraform, tags are used to organize and categorize resources within the cloud infrastructure. 

  • In GCP, Terraform tags are used to add metadata to resources such as virtual machines, disk, and networks. These tags can be used to identify, organize and manage resources within GCP. For example, you can use tags to organize resources by environment, application, or project, and you can also use tags to identify resources for billing and cost management.
  • In AWS, tags are used similarly to GCP, but they are referred to as resource tags. AWS tags provide a way to organize and categorize resources within an AWS account.

In summary, the feature fixed the handling of tags in the Google Cloud Provider (GCP) for Terraform, which were not working correctly, resulting in broken functionality. Terraform tags are used to add metadata to resources such as virtual machines, disk, and networks within GCP, and in AWS it's referred to as resource tags. They are used to organizing and categorize.

Start using tags the proper way with Brainboard.
🎨 Design area
7 months ago

␡ Deleting an item in map deletes all items

The issue being addressed is that when a user added key-value items into a map-like tag and then removed only one item, it would delete all the items in the map.

The development team has fixed this issue and now when a user removes one item from a map, it will only delete that specific item and not all the items in the map. This ensures that users have greater control over the items in their maps and can make changes to them without accidentally deleting all the items.

In summary, this feature addresses a bug in Brainboard where when a user added key-value items into a map-like tag and then removed only one item, it would delete all the items in the map. The development team has fixed this issue and now when a user removes one item from a map, it will only delete that specific item, ensuring that users have greater control over the items in their maps and can make changes to them without accidentally deleting all of the items.
🎨 Design area
7 months ago

␡ Can’t delete a local*

The issue being addressed is that users were unable to delete locals, which are variables with a scope of "local".

The development team has fixed this issue and now users are able to delete locals. This means that users can now delete variables with a scope of "local" without encountering any errors.
*In Terraform, a local is a way to assign a value to a variable, and it's only accessible within the same module where it's defined. A local variable can't be accessed outside of the module where it's defined. It can be used to store temporary values that are used within a module and it's not exposed to other modules.
For example, in Brainboard, a user could define a local variable to store the name of a resource and use it throughout the module, and then delete it when it's no longer needed.

In summary, the bug fix addresses an issue where users were unable to delete locals in Brainboard. Now, users can delete variables with a scope of "local" without encountering any errors. Locals are variables with a scope of "local" in Terraform, and it's used to store temporary values that are used within a module and it's not exposed to other modules.
🎨 Design area
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.
🎨 Design area
8 months ago

🐞 Auto-generate the Terraform code

The issue being addressed is that the code was not being generated for a new architecture.

The development team has fixed this issue and implemented auto-generation of Terraform code, which is a first in the cloud computing industry. This means that when a user creates a new architecture in Brainboard, the platform will automatically generate the corresponding Terraform code for that architecture diagram.

This auto-generation feature can help cloud architects go faster in designing and deploying cloud architectures. By having the Terraform code automatically generated, cloud architects can save time and effort that would have been spent on manually writing the code. This allows them to focus on other important tasks, such as designing and testing their architectures.

Additionally, the auto-generation feature can also help to reduce the chances of errors that can occur when manually writing code. By having the code automatically generated, the chances of typos, syntax errors and other issues are greatly reduced, which can lead to a more stable and reliable infrastructure.

In summary, the feature fixed the issue where the code was not generated for a new architecture and implemented auto-generation of Terraform code, the first in the cloud computing industry. This auto-generation feature can help cloud architects go faster in designing and deploying cloud architectures by saving time and effort that would have been spent on manually writing the code, and reducing the chances of errors.
🎨 Design area
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.
🎨 Design area
11 months ago

⬇ Export your diagram into svg, png or pdf

The feature being mentioned in this statement is the ability to export architecture diagrams in Brainboard, a cloud management solution, into various file formats, such as SVG, PNG, or PDF. This feature allows users to save their diagrams in a format that is compatible with various image editing and presentation software.

The export feature allows users to take a snapshot of their current architecture diagram and save it as an image file, which can be useful for sharing with others, such as a boss or team members, or for keeping a record of the diagram for later reference.

Additionally, this feature also allows users to export their diagrams in different formats, like SVG, PNG and PDF. SVG format is vector based format which can be zoomed without losing quality, PNG format is raster based format which can be used for images, PDF format is used for document sharing. Users can choose the format according to their needs.

The statement also mentions that the export feature has been reintroduced, indicating that it may have been removed or absent in previous versions of Brainboard. This feature is also useful for those who missed the Screenshot feature, which is now back and improved. With the export feature, users can quickly export their cloud architecture diagrams and drop it anywhere they would like, such as in a presentation or in an image editing software for further annotation.

In summary, this feature allows users to export their architecture diagrams in Brainboard into various file formats, such as SVG, PNG and PDF, enabling them to save and share their diagrams in a format that is compatible with various image editing and presentation software, and it also allows users to take a snapshot of their current architecture diagram and save it as an image file.

Start exporting your cloud architecture on Brainboard.
Screenshot 2022-03-08 at 10.51.18.png 115.92 KB

You can export your architecture as an image (svg, png or pdf).
🎨 Design area
about 1 year 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 connector.link.type): 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 connector.link.type.
  • 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