Have a feature in mind that you think would benefit you and your business? Fill out our feature request form and let us know! You can also vote on existing requests to help us prioritize them in our development roadmap. Your input is valuable to us and we strive to build the best product for you.
We value your feedback and strive to build the best product for you. You can vote on existing posts, discuss them with other users, or even add your own feature request on our platform.
Powered by FeedBear
The ability to pop out the code window from the architecture window. Popping out of other windows as well would be helpful when working with multiple monitors
When you click on the project menu on the main screen, it would be very helpful if it would show you the list in the last modified date, or allow you to filter by newest to oldest modified. This way if you have lots of projects you can easily access the the last one to be modified as it will appear at the top left of the screen. Even though I can see that it shows the projects in date order, I know that I have modified a project more recently, but it is not showing at the start of the list.
The dark mode is a feature that changes the color scheme of an interface to a darker background with light text and elements. This feature reduces eye strain and improves visibility in low-light conditions. Brainboard will support dark mode sooner or later, where the background color is dark, and the foreground color (text, elements) is light. This can help you be more comfortable working on the platform in different environments.
Terragrunt is a thin wrapper that provides extra tools for keeping your configurations DRY, working with multiple Terraform modules, and managing remote state. Terragrunt functionality is similar to Terraform workspaces, but Terragrunt is much more elegant and robust. https://terragrunt.gruntwork.io/ https://github.com/gruntwork-io/knowledge-base/discussions/92
Terraform Provider: VMware is a plugin for the Terraform infrastructure as code tool that allows users to manage their infrastructure on VMware vSphere, which is a virtualization platform that allows to run virtual machines on top of physical servers. The provider provides a set of Terraform resources that map to VMware vSphere services and objects, such as virtual machines, networks, and storage volumes. With the VMware provider, users can write Terraform configurations that define their infrastructure and then use Terraform to create, update, and delete those resources on VMware vSphere. The future integration of Brainboard with Terraform Provider: VMware, in addition to its current support for AWS, GCP, OCI, and Azure, will allow users to use Terraform to provision and manage their VMware vSphere infrastructure using a visual interface. This can help users who are more familiar with VMware to use Terraform to define their infrastructure and manage it with Brainboard. The integration will also provide access to VMware vSphere's advanced features such as virtualization, storage and networking. This will give users more flexibility in choosing the best tool for their specific use case and improve the overall experience.
Add tflint as a plugin to use in the pipeline
This feature request is asking for a way to import diagrams created in Visio or Lucid Charts into Brainboard. The goal is to use the diagrams as a starting point for creating Terraform code, and then be able to share the resulting code with infrastructure engineers. Essentially, it is a way to bridge the gap between the visual representation of infrastructure and the code used to provision it. This would help streamline the process of creating Terraform code and make it easier to collaborate with other members of the team.
Pulumi is an open-source platform for infrastructure as code (IAC) that allows developers to use familiar programming languages and concepts to define and manage their cloud infrastructure. Like Terraform, Pulumi allows users to provision and manage cloud resources using code rather than a web console or command-line tools. Pulumi is similar to Terraform but it uses programming languages such as JavaScript, TypeScript, Python, and Go. This allows developers to use their existing skills and tools and to take advantage of existing libraries and frameworks. The future integration of Brainboard with Pulumi and its current support for Terraform will allow users to use Pulumi as another alternative to provision and manage their cloud infrastructure using a visual interface. This can help users who are more familiar with programming languages to use Pulumi to define their infrastructure and manage it with Brainboard. The integration will also provide access to Pulumi's advanced features such as cross-resource dependencies, and support for different cloud providers. This will give users more flexibility in choosing the best tool for their specific use case and improve the overall experience.
Using AWS 5.16.2 to deploy to AWS cloud. The resource names are not added as tags to the terraform code object automatically. This results in objects being created with an alias name of just - and makes wandering through the AWS console more difficult. Please automatically add the resource name from the design as a Name = <resource_name> tag to each nameable object.
Since you generate Terraform code. Can you also provide security scan using TFSec or Checkov. Also OCI generation. You can keep this as a premium feature.
We are using Azure Bicep to model our infrastructure. We would like to use Bicep instead of Terraform
The Terraform OpenStack provider is a plugin for the Terraform infrastructure as code tool that allows users to manage their infrastructure on OpenStack, an open-source platform for building and managing cloud environments. It provides a set of Terraform resources that map to OpenStack services and objects, such as servers, networks, and volumes. With the OpenStack provider, users can write Terraform configurations that define their infrastructure and then use Terraform to create, update, and delete those resources on OpenStack. The provider supports all OpenStack services that have a corresponding Terraform resource. This includes Compute (Nova), Identity (Keystone), Networking (Neutron), Object Storage (Swift), Block Storage (Cinder), Load Balancer (Octavia), DNS (Designate), and others. This provider allows users to leverage the power of Terraform and its state management, provisioning and orchestration capabilities while using OpenStack as their cloud provider. It also allows to use other Terraform providers to manage other parts of the infrastructure, like DNS, load balancer, etc.
I have my terraform setup through common modules, load balancer, ec2, ecs, postgreSql, etc... I also have a folder structure for the environments and a common parent. I'd like to import these modules using a folder and then pull in those modules. those folder have the same filenames: variables.tf, main.tf
We need support for Terraform workspaces, so we can scale the code across multiple environments.
One feature of Brainboard is the ability for users to compare two cloud infrastructures side-by-side to see versioning changes, code reviews, cloud optimization, and security checks. This allows users to quickly identify changes made to their cloud infrastructure and compare the current version to previous versions. This feature provides several benefits for both cloud architects and stakeholders. For cloud architects, it allows them to quickly identify and track changes to their infrastructure, making it easier to manage and maintain their cloud environment. They can also use this feature to perform code reviews, ensuring that changes are made according to best practices and that there are no potential issues with the infrastructure. For stakeholders, the feature provides transparency and visibility into the cloud environment, which can help them make more informed decisions about their infrastructure. They can also use this feature to identify areas of the infrastructure that may need optimization or security enhancements and make recommendations accordingly. Overall, having this level of visual understanding in one solution for cloud architects and stakeholders improves the efficiency, security, and reliability of the cloud infrastructure and allows for better-informed decisions about the organization's infrastructure.
Enrich Your Cloud Management Journey Transition from traditional methods to an intuitive, visual interface for managing IBM Cloud infrastructure using Terraform, backed by Brainboard's integration. Holistic Infrastructure Management Delve into managing compute instances, networks, storage volumes and more on IBM Cloud with Terraform configurations, augmenting your control over cloud resources. Seamless Provisioning and Management The integration facilitates easy provisioning and management, ensuring a smooth, visual experience for users familiar with IBM Cloud and Terraform. Access Advanced IBM Cloud Features Unleash the potential of IBM Cloud's advanced features including virtual servers, storage, and databases, enhancing flexibility and improving the overall cloud management experience.
From the request: Add recommendations based on Best Practices / Well Architected frameworks. This feature will provide recommendations and warnings to users while adding resources. These recommendations will cover best practices in various areas, such as networking, security, and cost optimization. This feature aims to assist users in making informed decisions and ensuring that their infrastructure is set up in the most efficient and secure way. It will guide in real-time while configuring the infrastructure, allowing users to make adjustments and improve their infrastructure. This feature can help users to avoid common mistakes, improve the performance and security of their infrastructure and save costs.
A tfvars file (Terraform variables file) is a file used to define variables for a Terraform configuration. These variables are used to parameterize the Terraform configuration, allowing you to reuse the same configuration for different environments or use cases. The tfvars file is a plain text file that typically uses the .tfvars file extension, and it contains key-value pairs that define the variable name and its corresponding value. For example, if you have a variable called region that you want to set to us-west-2, you would create a tfvars file that contains the following: region = us-west-2 You can also define variables in the Terraform configuration file itself, but using a separate tfvars file allows you to keep the configuration file more organized and to easily change variables without modifying the configuration file. You can use a tfvars file by passing it as an argument when you run Terraform commands. For example, to run terraform apply and use the variables defined in a myvars.tfvars file, you would run the following command: terraform apply -var-file=myvars.tfvars It's important to note that Terraform also allows you to use environment variables, CLI flags and other means to pass variables and the use of tfvars file is just one of the many ways to pass variables to Terraform.
When you're company is part of a larger group of organisations, it would be nice to be able to share architecture templates with the other organisations in the group (partner organisations). This is not possible today as a template is either Public or Private. What is needed is a way to share a template with selected organisations.