Thank you for your vote, register to receive notifications and updates
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.
We have enhanced the Git integration feature, which now commits changes via Terraform operations using your user's email. This improvement aligns actions with the user's identity instead of the app itself, following the user-on-behalf authentication flow detailed in GitHub's documentation.
To facilitate this process:
Organization owners or admins are required to authenticate the GitHub application.
Post-authentication, users will create git_credentials through an OAuth process via the configured GitHub app.
We will develop documentation to guide through GitHub configuration.
A migration plan for current GitHub-using customers will be prepared, including backend and frontend implementation of the new flow.
User-friendly error messaging will be added to assist with migration and credential expiry issues.
We crossed a huge milestone here and we opened our API that enables you to programmatically interact with Brainboard to do different actions:
Create a project
Create envioronment
clone a template into a specific project or environment
update variables
and deploy the infrastructure
This API is particularly useful for integration with platforms like ServiceNow, allowing external automation and management of modules or projects within Brainboard.
We listened to your feedback and just added Kubernetes terraform provider. You can now design your Kubernetes architecture and deploy it from Brainboard.
Checkov Integration: Checkov is now reintegrated, enhancing our security scanning capabilities.
OPA Job Status: We've improved the OPA job status to now fail when the result is empty, ensuring more accurate feedback.
New Status for Partial Success: Responding to your requests, we've added a new status for scenarios where the job or pipeline succeeds despite some jobs failing.
Visual Enhancements: All job and pipeline statuses have been updated with new colors and icons for clearer visual representation.
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
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.
Brainboard now enables users to authorize individuals to customize the branch source, allowing them to create multiple pull requests of a single architecture effortlessly. customize git source
Pull request plugin in the CI/CD workflow: We are excited to announce the successful integration of a new feature within Brainboard's CI/CD workflow - the Pull Request (PR) plugin. This integration empowers users to trigger PR creation directly within their Brainboard workflow, streamlining the development process and promoting collaboration among team members.
Legacy use-case: If you use Terraform or IaC to deploy your infrastructure, you either need to have the tests locally (heavy to maintain) or push to the CI and do tests there (you spend your time waiting).
✅ With Brainboard, you can make sure that your work is clean BEFORE you push into git by using the robust CI/CD engine to check while you are building the infrastructure
For e.g. do security checks, cost estimations, policy enforcement then automatically do a PR if all checks are green.
We're excited to announce that the CI/CD Engine has been improved with new features to improve infrastructure management for our users.
One of the most exciting new features is the drift detection capability, which allows engineers to stay on top of their infrastructure by notifying responsible parties in case of drift, scheduling workflows for better optimized timing, and maintaining order while another workflow is active. Drift Detection output with a change detected
Other new features include:
Multiple workflows: With Brainboard's CI/CD Engine redesign, you can now create multiple workflows, providing greater flexibility and customization options for designing and implementing projects.
CI/CD workflow templates: With Brainboard's CI/CD Engine, you can create workflow templates that you and your team can reuse to streamline your workflow and optimize your infrastructure management.
Scheduled workflows: Brainboard's CI/CD Engine allows you to schedule workflows to be launched at any desired time. This ensures that workflows are being executed at the best optimized timing for your infrastructure management needs.
Notifying on pipeline failure: Notifying someone when drift is detected on cloud infrastructure can help prevent issues such as security vulnerabilities, compliance violations, and performance problems. By detecting drift early and addressing it promptly, IT teams can investigate and remediate any issues before they cause substantial damage, ensuring that the infrastructure remains secure, reliable, and operating as expected.
These features provide greater flexibility and customization options for engineers when designing and implementing projects.
We understand the importance of ensuring infrastructure security and reliability, and these new features were designed with that in mind. We hope that our users will find them useful in streamlining their workflow and optimizing their infrastructure management.
In the CI/CD Engine, we've been adding approval tasks enabling cloud architects to ask for review / approval before, during or after the deployment. Now, this task has improved, enabling seamless email notifications.
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.
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.
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.
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.
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.
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.
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.
*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.
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.
.gif)
