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.
As we completely redesigned the Members page, you can, now, view and edit member specifications on the right-hand panel. Additionally, this menu item will not be displayed for users with pending invitations, providing a smoother user experience.
Brainboard is now configured to dynamically support all versions of OpenTofu released on GitHub, including alpha, beta, and release candidates. This update ensures you can select any OpenTofu version for both architectures and workflows, providing greater flexibility and compatibility.
As a refresher, the latest version of OpenTofu (1.7.1) introduces several significant enhancements:
Key features of this release include end-to-end state encryption to ensure the security of your configuration files.
Dynamic provider-defined functions for more flexible resource management.
As you build and grow your cloud architectures, environments, and projects, it’s important to structure the data and have an efficient and easy way to navigate the information. That’s why we rebuilt the project, teams, and members pages from scratch.
This new intuitive UI will help you easily understand the relationship between different objects, like which projects a specific team has access to or which different teams a user belongs to and with what roles (RBAC).
No matter how complex your organization is, you’ll be able to browse the information in a consistent way.
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.
→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.
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.
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.
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.
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.
Assume role: The most commonly used method to connect a third party to your AWS account is now available in Brainboard. This is the most secure way to allow Brainboard to perform actions on your behalf within your account.
Access & secret keys: You can still use IAM user with access / secret keys.
At Brainboard, we like to rework existing features while improving them at the same time.
1. New User Interface (UI)
Experience a sleek and intuitive design that enhances user interaction and efficiency when giving permissions, managing roles & inviting new members to collaborate.
2. Enhanced Role Management
Streamlined process to manage roles and their associated permissions.
Directly link permissions to your specific environment, architectures, and workflows for a tailored experience.
3. Granular Permission Control
Dive deeper into permission settings with the ability to narrow down permissions at various levels:
Organization Level: Control and delegate access across your entire organization.
Architecture Level: Define permissions specific to different architectures within your setup.
Project Level: Ensure the right people have the right access for individual projects.
We are thrilled to announce a new security feature! To further protect your account and data, Brainboard now allows you to enable or disable Two-Factor Authentication (2FA) at your discretion.
2FA adds an extra layer of security to your account, ensuring that you're the only person who can access it, even if someone knows your password. It's a simple, effective way to prevent unauthorized access.
We strongly recommend enabling 2FA to keep your Brainboard account as secure as possible. After all, your peace of mind is our priority!
Stay safe and keep building amazing things with Brainboard! 🚀
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.
Multi-Workflow Capability: You can now create and manage multiple workflows for your CI/CD pipeline, making it easier to organize and streamline your development process.
Drift Detection: Our new drift detection feature helps you identify and resolve configuration differences between your development, staging, and production environments.
Notification Sending: You can configure notifications to be sent to relevant stakeholders, keeping everyone informed about the status of builds, deployments, and releases — including when pipelines fail.
Approval Tasks: We’ve introduced approval tasks to enable more granular control over the deployment process. This feature lets you define a set of approvers who need to sign off on each deployment before it can proceed.
Scheduled Deployment: You can now schedule deployments for a specific time and date, allowing you to plan ahead and ensure that new releases are rolled out at a time that suits your team and your customers.
*Keycloak is an open-source identity and access management solution. It is designed to provide a centralized location for managing user authentication and authorization. Keycloak provides features such as Single Sign-On (SSO), user management, and access control for applications and services.
The feature being mentioned in the statement is the integration of Keycloak with Brainboard, a cloud management solution. With this integration, users of Brainboard have the ability to use Keycloak as the authentication system for their Brainboard account. This allows users to use their Keycloak credentials to log in to Brainboard, rather than having to create and manage separate login information.
By using Keycloak as the authentication system, Brainboard users can take advantage of Keycloak's advanced security features and user management capabilities. This can improve the security of the Brainboard platform and make it easier for users to manage access to their cloud resources.
In summary, the integration of Keycloak with Brainboard allows users to use Keycloak as the authentication system for their Brainboard account, which improves security and user management capabilities.
.png)
.png)
Powered by FeedBear