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.
🚀 CI/CD Engine
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
🚀 CI/CD Engine
about 1 month ago

🔐 We improved web socket* error handling in the CI/CD Engine!

All-in-one


Improve the error handling in the CI/CD (Continuous Integration/Continuous Deployment) engine of Brainboard. Specifically, the improvement is related to the handling of errors that occur during the use of web sockets.
*Web sockets are a technology that allows for real-time, two-way communication between a client and a server over a single, long-lived connection. In the context of CI/CD, web sockets may facilitate communication between Brainboard's CI/CD engine and other system components, such as the version control repository or the deployment pipeline.
The improved error handling in this feature ensures that any errors that occur during web sockets are handled more effectively, allowing a seamless CI/CD process to continue functioning even in the event of an error.
🚀 CI/CD Engine
2 months 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.
🚀 CI/CD Engine
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
🚀 CI/CD Engine
5 months 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.

🚀 CI/CD Engine
7 months ago

🚀 Do not commit/push .terraform/ folder during PR/MR

The feature being mentioned in this statement is related to the management of the .terraform/ folder in Brainboard, a cloud management solution. The issue being addressed is that when a pull request (PR) or merge request (MR) is made, too many files were being pushed, including the .terraform/ folder and its contents, such as terraform.tfstates.

The development team has implemented a feature that prevents the .terraform/ folder from being committed or pushed during a PR or MR. This means that when a user makes a PR or MR, the .terraform/ folder and its contents will not be included in the changes being pushed to the remote repository.

The .terraform/ folder is used to store the state of the resources in your Terraform configuration and it's sensitive data. So, it's not recommended to share it with others. By not committing/pushing this folder during PR/MR, it ensures that sensitive data is not accidentally shared with others, and it also reduces the amount of data being pushed, which can improve the performance of the PR/MR process.

In summary, the feature prevents the .terraform/ folder from being committed or pushed during a pull request or merge request in Brainboard. This ensures that sensitive data is not accidentally shared with others, and it also reduces the amount of data being pushed, which can improve the performance of the PR/MR process.
🚀 CI/CD Engine
7 months ago

🔥 Fix Terraform version change in deployment*

The issue being addressed is that when a user changes the version of Terraform to a newer one, the backend prompts them to migrate the state, but the version of Terraform is not updated in the frontend.

The development team has fixed this issue and now when a user changes the version of Terraform, the version is also updated in the frontend, and the user is able to perform actions such as plan, apply and destroy. This ensures that the user is always working with the correct version of Terraform, which can prevent errors and improve the stability of the platform.
*Terraform deployment is the process of creating, updating and deleting resources in an infrastructure, using Terraform HashiCorp Configuration Language (HCL) and Terraform API.

When you run terraform plan command, it compares the current state of infrastructure with the desired state, defined in the Terraform code, and it shows the changes that will be made to the infrastructure.

When you run terraform apply command, it applies the changes, defined in the plan to the infrastructure.

When you run terraform destroy command, it removes all resources, defined in the Terraform code from the infrastructure.

During this process, Terraform keeps track of the current state of the infrastructure in a state file, which is usually stored in a remote backend, such as AWS S3, and it can also be stored in a local file.

In summary, the feature fixed the issue with Terraform version change in deployment, where the version of Terraform is not updated in the frontend, causing difficulties for users to perform actions like plan, apply and destroy. 

Version and deploy your cloud architecture with Brainboard.
🚀 CI/CD Engine
8 months ago

✚ Git integration: Bitbucket*

*Bitbucket is a Git-based source code repository hosting service owned by Atlassian. It allows users to store, manage, and collaborate on their source code projects, using Git as the version control system. Bitbucket supports both public and private repositories, and provides features such as pull requests, code review, and issue tracking to help teams collaborate on code development.
The feature of integrating Bitbucket into the workflow means that users can now connect their Bitbucket repositories to other tools and services that they use, so that their code and development process can be seamlessly integrated into their overall workflow. This could include integrating Bitbucket with continuous integration and continuous delivery (CI/CD) tools, project management tools, or other code collaboration tools.

For example, users could connect their Bitbucket repository with a CI/CD tool like Jenkins to automate the process of building, testing, and deploying their code. They could also connect Bitbucket with a project management tool like Jira to track issues and tasks related to their code development process.

By integrating Bitbucket into Brainboard, users can streamline their development process and increase efficiency by eliminating the need to manually switch between different tools and services. Additionally, it can also facilitate collaboration and communication among team members by connecting their tools and services.



 
🚀 CI/CD Engine
about 1 year ago

🚀 GitHub Integration

Integration of GitHub and GitLab with Brainboard. Brainboard is a tool that allows users to design and manage their infrastructure as code. With this new native integration, users can now automatically push the code generated by Brainboard to their preferred Git-based repository, such as GitHub or GitLab.

This integration allows users to benefit from the capabilities of Brainboard, such as visualizing their infrastructure and generating Terraform code, while also being able to store their code in a trusted repository. By storing their code in a repository, users can take advantage of features such as version control, code review, and collaboration.

Brainboard already supports other Git-based repository hosting services, such as Bitbucket and Azure DevOps. This means that users have multiple options for where to store their code and can choose the repository hosting service that best fits their needs and workflow.

The feature also states that Brainboard continues to integrate the infrastructure with today's workforce, without jumping the whole team into Gits. This means that users can use Brainboard to design and manage their infrastructure as code, without needing to be experts in Git or other repository hosting services. This feature is meant to make it easy for users to take advantage of the benefits of infrastructure as code, even if they don't have a lot of experience with Git or other repository hosting services.