• Toaster/Notification Improvements: Adjusted the toaster component to have a 5s timeout, and moved it to the best place in the app: the bottom right. We also added a "Close all" button for multiple toasts, preventing duplicate notifications, and ensuring new toasts push up existing ones with right-to-left animation.
• Teams and project creation: We fixed a few issues related to creating teams and projects: teams name is case-insensitive now, prevent deleting the last of a project as it will lock access and better handling of project creation errors.
• Team Improvements: Resolved the issue where a user with a custom organizational role was missing from the table, causing incorrect layout display when there are 4 teams.
• Import CP AWS: We fixed different issues on AWS resources when importing from the provider, and we increased the coverage of the supported resources that you can import as we use now the native resource listing of AWS through resource explorer.
• Project description update: Even the smallest bugs, we make sure to fix them. We fixed the issue related to the description of the project that wasn’t saved properly during updates.

• 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.
• Loopable import.

We completely redesigned the profile page, adding new functionalities, enhancing the UI, and providing useful information about the user’s activity.

• Recent architectures and updates
• Team memberships and associated projects
• Comprehensive overview of the user's activity and roles.

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.

Main use-cases:

• →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

Private self-hosted runner

Service catalog — producer consumer

Private registry support

Module’s identity card persisted after a version change

Identity card - Field switch between raw and list

Copy a template in-architecture fixes

Smart inheritance: support of for_each and count improved

• Adding a new AD group, or AD user or refer to existing ones
• Create new AD policies
• Manage AD identity and application accesss
• and much more

You have now a Terraform state management dashboard.

 

• See your tfstate and fetch the latest version from your remote backend (if you are not using the default one)
• Manipulate it to import / add or remove resources
• List the resources inside
• Move it
• Execute Terraform actions on it.

• Websocket reconnection fixed: We have resolved the issues related to websocket reconnection in Brainboard. With this update: you no longer need to manually refresh the page to reconnect, enhancing the continuity of your Brainboard experience.
• Output deletion issue: We've resolved an issue in Brainboard where you were previously unable to delete outputs due to the smart deletion modal being incorrectly activated; it is now limited to only input variables and locals.
  • We are put back the suggestions’ list in the output fields that’s allows you to reference existing resources’ exported attributes.
• We have implemented fixes for three issues in Brainboard's copy-in-arch feature:
  1. We've ensured that copying within architecture retains the original resource names from the template, addressing the issue where names were unintentionally changed.
  2. We've resolved an issue where output values were incorrectly replaced when importing a template into an existing architecture.
  3. When cloning in-architecture from the template catalog, we now correctly import variables, prevent overlap with existing nodes, and optionally select all new nodes.
• Update CICD workflow description: We've addressed a usability issue in Brainboard's CI/CD workflow configuration where the 'Save and close' button was not visible due to a hidden overflow, ensuring the button is now always visible for updates.
• GCP IAM resources: We has released an update to the GCP Terraform provider, now featuring GCP IAM resources. 

• 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.

• Create a project
• Create envioronment
• clone a template into a specific project or environment
• update variables
• and deploy the infrastructure

1. You now have a complete list of files that you can exclude from the PR.
2. Your selection will be persisted along with your git configuration.

Enterprise customers now have a complete self-hosted runner documentation available here.

Deployment Methods:

• Docker Compose: For users preferring Docker, we've provided sample Docker Compose and runner configuration files, simplifying the deployment process. The Docker image is hosted on our public Docker registry on GitHub, facilitating straightforward access and deployment.
• Kubernetes Deployment: For those utilizing Kubernetes, we introduced a Helm chart to deploy the self-hosted runner within their Kubernetes clusters. This chart is available in our public Helm chart repository, featuring detailed documentation, customizable values, and the required steps for installation and runner registration with Brainboard.

• Fixed an issue where jobs were sometimes picked by two runners within the first 3 seconds.
• Resolved a problem where changes to node graphics were not being saved correctly.
• The Terraform code is now automatically refreshed after deleting a node.

What to expect:

• Allow you to instantly visualize your terraform code with high quality precision, instead of rigorous and laborious manual creation.
• Full support of terraform modules.
• In the first version, only AWS will be supported.
• Available as a CLI that can be executed in your CI/CD to generate a picture of your infrastructure.

• 🪪 🔍 ID Card Search Enhancement: Now, when you search for any configuration, you'll receive the entire block of related configurations. This improvement ensures that if even one field within the block matches your search query, you'll get all the relevant information at once.
• ✍️ Dynamic Resource Naming: We've upgraded the resource naming mechanism. Now, the resource title is dynamic. The new default title is the resource name and you can override it.
• 🏃‍♂️ Refined the Nodes movements: We enhanced both the precision and the way you click and move nodes even in multiple selections. 

• 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.
• API-Triggered Pipelines: Boost your workflow efficiency with the ability to trigger pipelines via API. For enabling this feature, please contact our support team.

• Our new IPs, starting 2024-01-16 10:00 UTC, will be: 3.18.12.57, 3.19.117.9, 3.12.21.31, 3.140.65.244, 18.223.219.168, 3.139.254.14 
• Our current IPs, until 2024-01-16 09:59 UTC, are 18.222.81.57, 3.129.80.18, 3.129.98.6 

Commitment to Your Feedback: This year will be dedicated to integrating the valuable feedback you've shared with us. We're committed to refining and evolving based on your insights.

• ✨ Introducing Brainboard AI: We're excited to reveal early access to Bob, our AI-driven cloud kickstarter. Though initially planned for January 1st, 2024, we're rolling it out sooner! Request your access now and be among the first to generate cloud infrastructures (diagram + code) that you will be able to configure and test. 
• Career Opportunities: We're expanding our team! If you're passionate about AI and Infra-as-Code diagramming, we want to hear from you. Join us in shaping the future of Brainboard. Send your application to [email protected].
• You're Part of Our Big Picture: We promise to maintain our stride in delivering regular, high-quality updates in the design area, ensuring a seamless design ↔️ code experience. Plus, get ready for a plethora of new videos and interactive webinars throughout 2024.

• Revamped UI/UX for the ID Card: Experience a fresh, user-friendly interface with the ID card, now featuring a 'stick-to-top' header for easier navigation as you scroll.
• Resource Rotation on Design Canvas: Introducing the ability to rotate resources on the canvas, adding a new dimension to your design capabilities.

• Programmatic CICD Triggers: Elevate your workflow efficiency with API-triggered CICD processes. To activate this feature, please contact our support team.
• Connector Enhancements: We've implemented 20 significant fixes to our Connectors, ensuring a smoother, more reliable experience.

• Advanced Node Options Bar: Effortlessly access styling features like background color through our redesigned options bar. Located conveniently near your selected node(s), it's now just a click away for seamless customization.
• Versatile Contextual Menu: Right-click to discover a world of possibilities! Our new contextual menu houses all essential actions, from 'open cloud configuration' & 'hiding from code' to 'transforming into data', ensuring every action you need is right at your fingertips.

• One of the key improvements in this release is the enhancement of diagram generation for imported cloud resources. Brainboard now uses more advanced algorithms for resource positioning and connector routing, resulting in more optimal diagrams that accurately represent the relationships between resources.
• One of the most noticeable changes is that the nodes are no longer all stacked on top of each other, resulting in a cleaner and more organized layout.
• There have also been improvements in the containers/children relations in the design, making it easier to manage complex infrastructures.
• Brainboard now incorporates dynamic linking, which means that code is generated with live links between resources, allowing for more seamless interaction between resources.

✨ Brainboard AI: 

🧑‍💻 Edit Existing Resources: 

🌧️ Import from AWS

Join us in this webinar to discover how you can establish a producer-consumer workflow. Those who traditionally don't create, maintain, and worry about Infrastructure as Code (IaC) & Terraform, can autonomously deploy and destroy their own cloud infrastructure stacks.

• Scalable architectures using both vanilla Terraform resources and modules, and then how to templatize everything.
• A multi-environment strategy for any cloud infrastructure.
• Control and approval mechanisms through CI/CD and drift detection, and how to shorten the feedback loop.

• Screenshot: We've completely rethought this feature. You can download an accurate image of your architecture.
• Identity card (idcard): When you have the idcard open and resize the node then close the idcard, the node resizes back to the initial size. This bug is fixed!
• Git App: We fixed the edge cases with GitHub integration.
• Copy: You are allowed to copy a text from one action terminal output or terraform code.The name of your architecture is now included in your browser's tab name.
• Terraform modules: You have now the default values displayed in the idcard.
• Pull Request: When you create a PR, you can edit the commit message and filter out files you want to exclude.

PS: We are working hard on the idcard in the Design area, did you see it 👀?

Brainboard’s design area is smarter than ever before. Every time you drag and drop a resource, Brainboard will automatically update z-index and inheritance using cloud knowledge.

For Eg.

1. When you drag & drop a Vnet on top of a subnet, Brainboard will automatically set the subnet as the child of the Vnet.
2. Now, in your daily usage, you shouldn't need to use the following buttons: send to back/backward/frontward/to front anymore. Brainboard will manage that for you.

• When deleting a variable, you will have a warning message if the variable is still used!

• We fixed the UI to add/edit variable, the save/update button is always visible.
• We fixed many bugs on import: 
  • Import files: Empty string values are not removed on required attributes
  • Import files: Warning message when the TF files are invalid or not found is back for clarity.
  • Import files & Cloud: We iterate again on the enrichment phase of the import to have better parent/child inheritance like supporting multiple locations inside one Resource Group

• We fixed the bug when the One Action buttons were always disabled.
• You can now use heredoc (<<EOT) in custom code.
• Brainboard’s training guide is back!
• When cloning your architecture or publishing it to the marketplace, all the architecture’s versions are removed automatically.

In this alpha version, you can edit existing resources only. (cf. more information)

You still have to drag & drop new resources but then either you update them via the idcard or via the code. Every edits you do are reflected into the diagram 👀

1. Modify the value of an existing attribute for a specific resource, variable, or block within the Terraform code.
2. Introduce new attributes or blocks for configurations such as a resource, relationship, Terraform module filename, or a distinct architectural design.
3. Remove unnecessary attributes or blocks; the diagram will automatically update to reflect these changes.

• Enhanced Project/Environment Visibility: We appreciate the valuable feedback from our users and customers. If you encounter any ongoing issues, please don't hesitate to inform us.

• Streamlined Switch Node Resource Type: We've eliminated redundant code that no longer serves a purpose when toggling between resource and data source modes.
• Multi-User Mode Stability: We're pleased to inform you that the pesky blinking issue in multi-user mode has been resolved. 😉
• Search Bar Undo Functionality: You can now press Ctrl+Z to conveniently undo text changes in the left bar's search function.
• Enhanced Node Selection and Movement: We've addressed the issue where moving multiple nodes was problematic. We apologize for any inconvenience this may have caused.
• Brainboard File Restoration: Good news! The Brainboard_file feature is back and fully functional.
• Simplified CP Selection During Architecture Switch: When transitioning between different architectures, we've made it easier to select the right CP (Control Panel).
• 🥚 Infrastructure Migration to Kubernetes: Our infrastructure has been successfully migrated to Kubernetes, providing enhanced performance compared to the previous VM-based setup.

In the latest update, we have taken significant steps to increase trust and confidence in the Brainboard design area.

• You will experience a notable enhancement in reliability of the BB application, ensuring a smoother and more efficient workflow. 
• We have also ensured that all your work on the interface is automatically saved, providing you with peace of mind and enhancing productivity. 
• Our update allows users to understand and handle the cause of errors more clearly, promoting a more seamless and intuitive user experience. 
• The switch from one architecture to another is now more noticeable, allowing for easier navigation and operation within the application. 
• Furthermore, we have reimplemented the entire backend websocket management to ensure that bugs are a thing of the past. 
• This overhaul also brings an improved live status between the front and backend systems, ensuring real-time synchronization and communication for optimal performance and reliability. 

Dive into a modern and user-friendly design that simplifies your cloud connection process.

AWS

• 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.

Azure

• Certificate: Introducing a more secure way to authenticate with Azure using certificates. You don’t need to share your Azure AD app secret anymore.
• Client Secret: You can still use Azure AD app client secret.

1. AWS 5.16.2 Updates: We added this new major version, please check the breaking changes and migration guide if you are upgrading.
2. Azure Resources Icons: Thanks to valuable client feedback, we have fixed multiple Azure resources icons including Linux/Windows Function App, MySQL Server, and Databricks. Please continue to reach out to Brainboard support for any further icon updates.

   

3. Module Name Sanitization: Dragging and dropping modules now automatically sanitizes the module names from the catalog, preventing any unwanted characters or errors.
4. Resource Name Update: Updating a resource name is now more efficient. Brainboard will automatically update it everywhere, ensuring consistency across the platform.
5. Code Generation Bugs: Major code generation bugs have been fixed. Special characters are now supported everywhere, including in map's keys, enhancing the reliability of code generation.
6. Navigation in Readme File, ID Card, and Variable’s Description: The bug that prevented the use of the arrow down/up keys in the readme file, ID card, and variable's description has been fixed, allowing for smoother navigation.
7. Variable Description: Variable description is now multi-line ready, allowing for more detailed and organized descriptions.
8. Brainboard_shape Visibility: The accidental visibility of brainboard_shape in the code has been corrected.
9. Send Back Button: The design of the Send Back button has been enhanced to improve the design area experience.

• Experience a sleek and intuitive design that enhances user interaction and efficiency when giving permissions, managing roles & inviting new members to collaborate.

• Streamlined process to manage roles and their associated permissions.
• Directly link permissions to your specific environment, architectures, and workflows for a tailored experience.

• 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.

1. Enhanced Automatic Code Generation: We have refined our automatic code generation feature. It can now handle and manage much more intricate use cases, ensuring smoother and more efficient code generation for your projects.
2. Improved Handling of the Variable keyword optional with Default Values: Brainboard now supports the default value for optional object type attributes feature. This means you can seamlessly import a module or .tf file with variables that have an optional argument with a default value.
3. Addition of Meta-Arguments in the Extra Section for Modules: We've integrated the for_each/count/depends_on meta-arguments into the extra section for modules. This enhancement will provide you with more flexibility and control over your module configurations.
4. VSCode Integration in Variable Defaults and Values: We've made it easier for you to navigate within a variable's default or value. You can now use the arrow keys for this purpose. Additionally, we recommend using the mini code editor, similar to the one in the resource’s identity card, for a more streamlined experience.
5. Optimized Content Spacing: To enhance readability and user experience, we've adjusted the content spacing. This ensures that resources and resource titles do not overlap with the topbar or search bar, providing a cleaner and more organized view.
6. Automatic URL Detection and Formatting during your imports: Importing architectures or modules from Git repositories has never been easier! Simply copy the URL from your browser, and Brainboard will automatically detect and format it correctly for importing. This feature eliminates the need for manual adjustments and ensures an accurate URL for the import.

Before:

Now: 

➡ This update aims to improve your navigation and provide a more intuitive interface for all Brainboard users.

Brainboard now seamlessly integrates with the Azure DevOps Terraform Provider, enabling users to manage their Azure DevOps resources using Terraform through Brainboard’s intuitive design interface.

Click on the top left-corner to switch to it 😇

• Brainboard supports AWS, Azure, GCP & OCI.
• For unsupported TF provider, a workaround exist to use custom resources.

• Direct integration with the TF provider azure_devops. Users can now design, configure, and manage Azure DevOps resources right within Brainboard.
• Drag-and-drop interface for adding and configuring Azure DevOps resources such as repositories, pipelines, and service connections, directly within your infrastructure designs.
• Automatic generation of Terraform configurations (.tf files) for Azure DevOps resources, managed alongside your other infrastructure code, all within Brainboard.
• Visual mapping between Azure DevOps resources and other infrastructure components, enabling clearer and more efficient orchestration of multi-service environments.

• the Google Cloud Storage (GCS) Remote Backend integration.
• Generic HTTP remote backend
• Remote backend HTTP (for Gitlab)

The remote backend is a storage that hosts the Terraform state of your cloud infrastructure after it is provisioned. Read Brainboard documentation.

• Enhanced Storage: Store your Brainboard state within a designated prefix in your existing bucket, ensuring secure and scalable project management.
• Robust Infrastructure: Harness the power and reliability of the 'alpha' bucket for seamless project state management.

1. Configurable Prefix: Organize your storage by defining a unique prefix in the 'alpha' bucket.
2. Top-tier Security: Trust in 'alpha', one of the industry's leading cloud storage solutions, to maintain your project's integrity.
3. Effortless Integration: Set up with ease. Link your 'alpha' bucket, and let Brainboard do the heavy lifting.

1. Go to the remote backend settings page. (Settings -> Data)
2. Click on the 3 dots in the top-right corner of the configuration.

   

3. You can then select "whichever" backend and save.

1. Streamlined Resource Switching: We have addressed an issue where certain configurations were not being properly removed when switching a resource to data or vice versa. Now, the process is seamless, ensuring a smooth transition without any residual settings.
2. Enhanced Multi-Cloud Support: Our platform now features a switch button that remains accessible even if your current provider is different from the one you intend to switch to. This empowers users with multi-cloud architecture to efficiently manage their resources regardless of the provider.
3. Expanded Use Cases: We have incorporated feedback from diverse scenarios to cater to many more use cases effectively. This ensures our platform remains versatile and adaptable to various user requirements.

 

Indeed, the Brainboard team continues to operate remotely. 
All we need is our trusty laptops, isn't that right, BrainIaCs? 🙃

 

We've been tirelessly dedicated over the past two years to integrating your valuable feedback into our operations. In our efforts to continuously enhance your experience, we're thrilled to introduce several improvements, some even ahead of schedule:

1. Git Import functionality - This will streamline your code management by enabling user-friendly direct imports from Git repositories. We already have a first version that was released a year ago but now, the improvement is massive! 💥
2. Azure Import UI Enhancements - We will make constant improvements to ensure seamless interoperability with Azure. This includes updates to improve efficiency, security, and usability.
3. Role-Based Access Control (RBAC) V02 - We're stepping up our access management game, offering you greater control over who can access what within your projects.
4. Enhanced Security Connections with AWS & Azure - We've amped up the security measures for our connections with AWS and Azure, further fortifying your data security.

• 🥠 Azure Icons: Brainboard has been updated with the latest Azure icons from Microsoft Visio, ensuring that users have access to the most up-to-date icon library for seamless integration into their projects.
• 🧮 Remote Backend error: This update ensures that users no longer encounter vague internal error messages. Instead, they will receive clear, actionable feedback, making troubleshooting more efficient.
• 📂 Zip: Brainboard addresses compatibility issues by providing support for both Windows and Linux platforms, ensuring that the zip functionality works seamlessly on both operating systems, enabling users to effortlessly compress and extract files without any compatibility constraints.
• 🥡 Git flow: Brainboard enhances the workflow by optimizing the process of pushing existing Git repositories. With its improved flow, users can seamlessly execute Git pushes for repositories that already exist, streamlining the development process and promoting efficient collaboration.
• 🎴 Id card: Brainboard now offers improved ID card by automatically trimming spaces before and after words. This bug fix ensures cleaner and more accurate ID cards.

🔥 Releases: 

• Two new CI/CD Plugins enabling efficient collaboration and streamlined code reviews.
  • Pull Request: create directly inside your workflow/pipeline the Pull Request once all other validations and test pass.
  • Microsoft Teams: get a notification in your Teams once a pipeline succeed
• Unlimited Terraform code generation for free: You can enjoy the benefits of streamlining your design to code generation without any cost, making it an ideal choice for small-scale projects and personal use.
• Use markdown text in the design area: The enrichment text feature enhances the quality and context of written content and notes on top of your diagram, providing valuable insights and improving overall readability and comprehension of your infrastructure. 

🐞 Fixes: 

• Git configuration 
  • Git configuration now offers improved validation mechanisms to ensure the correctness of settings, reducing the occurrence of configuration errors.
  • The changes made in Git configuration are now saved automatically, eliminating the need for manual saving and preventing accidental data loss.
  • Instead of encountering scope conflict errors, Git configuration now notifies users of already existing errors, allowing for easier resolution and smoother configuration management.
• The new loading provides a seamless and responsive user experience, enhancing the overall efficiency of your Terraform configuration process.
• The cloud providers credentials forms and validation have been enhanced, making it easier to manage and validate credentials for cloud services.
• In the CI/CD output, auto-scrolling is disabled when users scroll up, allowing them to review and analyze the output without interruption.
• When removing all characters in the ID card field, the focus no longer disappears, providing a smoother user interaction and improving data entry experience.

🐞 FIXED by Batman 🦸🏻‍♂️

• Git Source Update: When using a module from a Git source, Brainboard automatically fetches the latest update. However, there are instances where this automatic update fails to occur. In such cases, manual synchronization is required to ensure the latest module version is obtained.
• Module Update Inconsistency: When making changes to a custom source module, Brainboard fails to update all architectures that use this module consistently. This leads to outdated module versions being used in some architectures.
• Improved Manual Synchronization: We have implemented enhancements to the manual synchronization feature for modules sourced from Git. Brainboard now reliably fetches the latest module update when initiated manually. This ensures that users have access to the most up-to-date version of the module.
• Inheritance System Issue: For a specific period of one day, there was a problem with the inheritance system. The issue caused inconsistencies and unexpected behavior when inheriting modules. However, the problem was identified and fixed on the same day.
• Code Fix for Network Ranges and IPs: We have resolved an issue related to code changes that involve network ranges and IP addresses. The fix ensures accurate handling and processing of these elements.
• Improved Variable Creation from ID Card Field: The process of automatically creating variables from the ID card field has been enhanced. The improvements aim to provide better accuracy and reliability when generating variables from this specific field.
• Import modules: When importing modules that already exist, we display the appropriate error message to better explain the root cause of the issue.
• Git Integrations: Error messages that prevented the saving of Git configurations have been resolved.
• Deploy: We noticed an issue with the Deploy tab causing infinite loading, which affected a few architectures. We resolved the problem immediately and apologize for any errors this may have caused and any impact on your deployment cycle.
• Terraform Plan: The Plan button was malfunctioning and displaying a warning about the concurrency limit, which was not intended. We apologize for any confusion or inconvenience this may have caused. The issue has been addressed and the warning will no longer appear.

⏮️ Rewind from Mike Tyson of the Cloud

• 🤖 Terraform X GPT: What to expect?
• 🤖 ChatGPT for DevOps: Best Practices, Use Cases, and Warnings

• 🦸‍♀️ The 3 most advanced Terraform commands made simple in Brainboard
• ⛅️ Moving to IaC: Challenges and Best practices
• 🧠 Become a Visual GUI: The New Era of Cloud Infrastructures
• 🌊 Writing Terraform custom code for unsupported resources in Brainboard
• 🚀 Become A DevOps Engineer in 2023: A Comprehensive Guide
• 🧱 Top 10 reasons your architecture library isn’t helpful and how to fix them
• 💲 FinOps: Techniques on how to save $7M of cloud cost

• 📌 Azure Eventhub hands-on with CI/CD workflow with Terraform, Tfsec, Infracost,Drift detection
• 🚀 Automating Multiple Environments with Terraform on Brainboard
• 💰 10x Faster Cloud Infrastructure Delivery: A FinTech Scaleup’s Success Story with Brainboard
• 🗺️ Azure Spring App Infrastructure-CI/CD workflow with Terraform, Tfsec, Infracost and Drift detection
• 🗺️ Azure Landing Zone Baseline & 4 Terraform open-source tools to make it secure and cost-efficient
• 🗺️ How to use Azure DNS Private Resolver + Terraform for securing your Azure Infrastructures**
• 🗺️ AWS EKS Kubernetes Cluster - Terraform+Tfsec+Infracost=Automate Cloud Cost & Security Management

🐞 FIXED by Batman 🦸🏻‍♂️

• Reuse Terraform modules already imported when importing a new architecture.
• Good news! Generic icons and logos can once again be easily moved by simply dragging and dropping them. 😎
• To zoom in on Zoom, Windows users can now use Ctrl + Scroll, while macOS users can use Cmd + Scroll.
• With the latest update to Import Terraform Modules, users can now seamlessly utilize their Git credentials even when they have just one credential available.
• You can now unlink Git configuration for pull requests from Brainboard.

⏮️ Rewind from Mike Tyson of the Cloud

• 🤖 ChatGPT for DevOps: Best Practices, Use Cases, and Warnings.
• 👨‍💻 No one should ever write a single line of Terraform code
• 🚀 Become A DevOps Engineer in 2023: A Comprehensive Guide
• 🧱 Top 10 reasons your architecture library isn’t helpful and how to fix them
• 🦸‍♀️ The 3 most advanced Terraform commands made simple in Brainboard
• ⛅️ Moving to IaC: Challenges and Best practices
• 💲 FinOps: Techniques on how to save $7M of cloud cost
• 🌊 Writing Terraform custom code for unsupported resources in Brainboard
• 🗺️ Azure Spring App Infrastructure-CI/CD workflow with Terraform, Tfsec, Infracost and Drift detection
• 🗺️ Azure Landing Zone Baseline & 4 Terraform open-source tools to make it secure and cost-efficient
• 🗺️ H**ow to use Azure DNS Private Resolver + Terraform for securing your Azure Infrastructures**
• 🗺️ AWS EKS Kubernetes Cluster - Terraform+Tfsec+Infracost=Automate Cloud Cost & Security Management
• 🌋 Disaster Recovery for cloud infrastructures with Brainboard
• 🚗 Terraform Drift Detection: How to monitor and remediate cloud infrastructure drift

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.

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.

Resources on Drift Detection: 

• Disaster Recovery for cloud infrastructures with Brainboard
• Terraform Drift Detection: How to monitor and remediate cloud infrastructure drift
• How the Cloud Can Bring Hope in Times of Crisis
• Improve Terraform Code Quality and Security of Delivery of Cloud Infrastructure Keeping the Same Engineering Velocity
• Why Drift Detection is Crucial for Successful Continuous Delivery Pipelines

🐞 FIXED

• The Terraform code refresh triggering event was completely revamped. If you encountered any issues regarding that, this is now fixed.
• Modules’ configuration have been fixed. You should always have your up-to-date modules’ variables.
• CI/CD terminal output can be as fast as your local environment. With all infrastructure-as-code IDE tools under one roof, there is no impact on velocity.
• Marketplace: You can now use your own Azure or AWS billing account / credits.

⏮️ Rewind

• 📌 Brainboard CI/CD designed specifically for the infrastructure
• 📌 Azure Landing Zone Baseline & 4 Terraform open-source tools to make it secure and cost-efficient
• 🛡 How to use Azure DNS Private Resolver + Terraform for securing your Azure Infrastructures
• 📌 AWS EKS Kubernetes Cluster - Terraform+Tfsec+Infracost=Automate Cloud Cost & Security Management
• 🔐Azure Sentinel+Terraform: 3 Key Benefits of Azure Sentinel for Protecting Your Azure Infrastructure
• 📌 AWS Landing Zone with Terraform - Save time with automated checks of your Terraform scripts
• 😍 Standardized Self Service infrastructure provisioning with Terraform - Easy Azure automation
• 👨‍💻 Boost your career as a cloud architect & DevOps with these top 9 Terraform Courses & Workshops
• Azure Multi Subscription Landing Zone - 6 Tips and Solutions for Cloud Architects and DevOps
• 🗺️ 🚀 3 reasons why AWS Elastic Beanstalk can help in overcoming deployment challenges
• ♻️ 5 Best Practices for Maintaining Consistency Across Cloud Environments

We've made some performance enhancements to the:

• 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.

• 

🧼 IMPROVED

We've made some performance enhancements to the:

• We are happy to announce that Brainboard is available for both: AWS Marketplace, Azure Marketplace
• Inheritance now supports multiple resources - While designing your cloud architecture, you can now move 2+ resources at the same time into a container.
• The Brainboard migration tool supports multi-lines strings.
• Export architecture as JSON - We added the export feature to allow all our users to either backup their architecture, to migrate them from one account to another one, to share them with the support when needed. You are now able to export and import any Brainboard architecture easily.
• Hide the default value for sensitive variables.
• Add the support of Terraform Cloud remote backend.
• All Terraform versions are now available in Brainboard CI/CD Engine.

🐞 FIXED

• You can now download / search the CI/CD output.
• We now list all your GitLab projects in Git configuration, before limited to 20.
• We fixed an error during pull request / merge request when the target branch already exists.
• Visual indicator when cloud resources are in Icon Only mode (Terraform code not generated)
• When using synced architectures, variables creation and updates are now synced to both / more architectures.
• We removed the issues linked to the scrolling and wrong colors on selection, in README.
• We removed quotes around ignore_changes (Terraform lifecycle options)
• Our new system will always choose the best Terraform file to show based on your architecture diagram.

⏮️ Rewind

• 📌 Brainboard CI/CD designed specifically for the infrastructure
• 🔐Azure Sentinel+Terraform: 3 Key Benefits of Azure Sentinel for Protecting Your Azure Infrastructure
• 📌 AWS Landing Zone with Terraform - Save time with automated checks of your Terraform scripts
• 😍 Standardized Self Service infrastructure provisioning with Terraform - Easy Azure automation
• 👨‍💻 Boost your career as a cloud architect & DevOps with these top 9 Terraform Courses & Workshops
• 🗺️ Azure Multi Subscription Landing Zone - 6 Tips and Solutions for Cloud Architects and DevOps
• 🗺️ 🚀 3 reasons why AWS Elastic Beanstalk can help in overcoming deployment challenges
• ♻️ 5 Best Practices for Maintaining Consistency Across Cloud Environments

🧼 IMPROVED

1. 

   Clearer output for clearer decisions: When deploying your cloud architecture, we improved the output of your Terraform code, CI/CD workflow and Terraform actions. That will enable you to make clearer decisions, apart from all distractions, having all your cloud environment in one solution.
2. New year, new design system: We've been shipping a lot lately. Our image you perceive of Brainboard count for us. So we heard your feedback and designed internally our new logo, images, and experience across the website, the onboarding, and the application with new colors and visual improvements. 
3. Documentation: A new documentation was just released, improving product clarification and explanation. This improved documentation will help users better understand our product and how to best use it. Get excited about next week's website launch, featuring brand-new features and a more modern design! You can visit the documentation here.

We are excited to announce the brand lifting of Brainboard's website! 

After 2 months of hard work and dedication, the new website is now live 🎉
Thanks to the whole Brainboard team, we were able to review all the content on time and deliver the best experience possible, maintaining the high quality we value for our customers, users and FFFs.

Let us know what you think, as we always look for feedback and 99.9% perfection 🙃

NB. We are also happy to inform you that further improvements are coming soon across the web application experience, so stay tuned!

Check out our new logo 👀

🐞 FIXED

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

1. Import errors:
   • The import functionality has been improved to address the problem of internal errors. Error handling has been optimized and the dependencies between resources are now managed more effectively.
2. CI/CD Approval task — List of suggested users: 
   • The user experience when deploying cloud infrastructure through the CI/CD Engine has been improved. Users now have the ability to choose from a list of suggested users when approving a task, eliminating mis-suggestions.
3. Configuring resources when selecting a node
   • The user experience has been improved when selecting resources through the Design Area or TF Code. Now, the ID Card will open automatically when clicking on a resource name.
4. Data inheritance not implemented when importing: 
   • The inheritance of data sources when importing TF files has been implemented. For example, when a data subnet is inside a data virtual network, it will now be depicted as such in the TF code.
5. Templates' catalog ownership:
   • The "by" section in the Template Catalog has been updated to include all relevant authors. This ensures proper attribution and recognition.
6. Initiator name is missing in pipeline output:
   • The name of the person triggering the pipeline is now included in the pipeline View, providing visibility into who is responsible for launching which pipeline and when.

🧼 IMPROVED

We've made some performance enhancements to the:

1. Performance: Performance in the canvas area of Brainboard has been improved gradually, especially with small architecture and very big architectures (500+ nodes). This should result in faster load times and a smoother user experience.
2. Documentation: A new documentation was just released, improving product clarification and explanation. This improved documentation will help users better understand our product and how to best use it. Get excited about next week's website launch, featuring brand-new features and a more modern design! You can visit the documentation here.

🐞 FIXED

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

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. 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. 
3. 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.
4. 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.
5. 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.
6. 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. 
7. Editing node title:

• 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.

🧼 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.

📆 Replay: Understand CI/CD strategies & Best Practices 

• 0:02:20 CI/CD Day
• 0:04:40 CI/CD in Application world 
• 0:07:00 CI/CD for the app  
• 0:13:47 IaC Best practices 
• 0:20:00 Application vs. Infrastructure 
• 0:28:00 IaC languages 
• 0:34:40 Existing solutions 
• 0:38:40 Commonalities & Challenges
• 0:42:10 What is expected from a CI/CD solution 
• 0:48:10 Some of useful open-source tools 
• 0:52:00 CI/CD Best practices 
• 0:57:40 Successful Implementation 
• 1:05:20 Brainboard CI/CD Engine—demo tour 
• 1:05:50 Design your first CI/CD workflow visually 
• 1:09:00 CI/CD outputs 
• 1:10:40 Create a CI/CD pipeline template

🐞 FIXED

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

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.

Before

Now

About

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 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. 

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.

Latest Terraform Providers' versions:  

In Brainboard, this applied for all cloud providers supported (Azure, OCI, GCP, Scaleway)

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.

variable "region" {
  default = "us-west-2"
}

resource "aws_instance" "example" {
  ami           = var.ami
  instance_type = "t2.micro"
  region        = var.region
}

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.

*Single tenant refers to a software as a service (SaaS) solution where each customer or client has their dedicated instance of the software running on a separate infrastructure. This contrasts with a multi-tenant SaaS solution, where multiple customers or clients share the same software instance, running on a shared infrastructure.


In a single-tenant SaaS solution, the customer's data and configuration are isolated from other customers and not shared with any other organization. This provides a higher level of security, compliance, and customization. Customers have more control over their data, and the software can be tailored to the customer's specific needs.


Single-tenant SaaS solutions are typically used by larger organizations with more stringent security and compliance requirements or organizations requiring a high level of customization. They may also be used by organizations with sensitive data that they do not want to share with other organizations.


It's important to note that Single tenant solutions are often more expensive than multi-tenant solutions because the hardware and infrastructure costs are spread across fewer customers. Additionally, because each customer requires its own infrastructure, there are more operational costs to manage and maintain the different instances.

*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

1. Reusability: Modules allow you to group resources and reuse them across multiple configurations. This can significantly reduce the code you need to write and maintain.
2. Organization: Modules provide a way to organize your resources and make your Terraform configurations more readable and maintainable.
3. Versioning: Modules can be versioned, which allows you to track changes and roll back to a specific version if needed.
4. Collaboration: Modules can be shared and used as a building block for other people's configurations. This allows for better collaboration within a team or community.
5. Abstracting complexity: Modules can help abstract away complexity by breaking down large configurations into smaller, more manageable pieces.
6. Better testing: By using modules, you can quickly test a specific part of your infrastructure without affecting other parts.
7. Scalability: Modules can help to scale your infrastructure more efficiently. They can be used to create reusable and composable infrastructure patterns which can be used across different environments.
8. Simplifying the management: Modules help to simplify the management of infrastructure by breaking down complex infrastructure into smaller, more manageable components.

Import your Terraform modules on Brainboard.

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 →

We listened to your requests and just added OCI (Oracle Cloud Infrastructure) to Brainboard, your one-and-only IaC solution! 

• You can use Terraform to interact with Oracle Cloud Infrastructure resources
• You can visually build your OCI cloud infrastructure and deploy it with ease
• You can import any existing OCI-based repo, public and private onto Brainboard
• You can convert all your OCI cloud infrastructures into reusable templates.

* 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.

Introducing Import Azure

• The location/Region field has been fixed to ensure that it accurately reflects the real value.
• We have fixed an issue where variables locals were not retained during the cloning process.
• The reminder form has been fixed to ensure proper functionality.
• The custom code field is now fully usable, as it was previously causing issues.
• The architecture cloning process now also retains locals values.
• We have resolved an issue where the deletion of modules from the catalog was not working as expected.

• 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.

• 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.

• Fixed: When I delete my current architecture, the interface freezes / infinite loop with error in console
• Fixed: When I add an Azure virtual network for e.g. and I remove a chip from tags, the interface resets, the code generated is completely broken and I have no way to open the resource again to fix it.
• Fixed: We can’t change the selected TF file to another one (other group tf file, variables, outputs, …)
• Fixed: When a user configure a block (set) then deletes all the value the block is generated empty. 
• Fixed: Subnet IDs double added
• Fixed: Automatically generate the connectors between resources when I reference an existing resource.
• Fixed: when I connect, it shows the owner as an extra user
• Fixed: With some attribute type like SelectList (array), changes do not trigger the TF code refresh
• Fixed: Sign up page on Safari browser 
• Fixed: In the README modal, the save button doesn’t work at all, so if I write content it is automatically saved and there is no need for this button.

*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.

• You have the ability to add blocks easily
• You have the ability to use multiple time the same block 
• You have the ability to upload files in the idcard
• ALL lifecycle are supported

• Split nodes into different files
• Import tfstate now is automatic and part of importing files
• Remove credentials in the module source URL -> security improvement
• Clone templates in the same architecture
• Fix graphical bugs to make the user experience enjoyable
• Allow emoji / any char in names (architecture, env, team, ...)

• Select group when selecting file
• Select the right file when opening the IDcard
• Group name validation improved

• Import module
• Import from GitHub/GitLab/…
• Everywhere else we support GitHub/AzureDevops

• 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.

*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 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.

• import module
• import from GitHub/GitLab/…
• Everywhere else we support GitHub/AzureDevops

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

*Frontend reload system refers to a technology that allows for automatic updating of the front-end (client-side) of a web application. It is used to ensure that users always have the most recent version of the application, without the need for manual updates.

1. Add a module
2. Edit the ResourceName
3. The change is applied and the new ResourceName just appeared in the code

• The locals part is added at the end of the variables table 
• Only name, scope, value, and description are used and visible 
• The description should be a comment before the local in the generated Terraform file

*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.

• Ask a mandatory team to invite member
• The default team is Admin on the default project
• UX improved for project create/update 

• Azure: block settings + feature block page
• AWS: block settings
• Hashicorp/vault: block settings (as you can see the address is required and not optional)

This feature is mainly for users that won’t deploy within Brainboard but already have their git and some TF provider settings.

1. Design
2. Design / Code vertical 
3. Design / Code horizontal 
4. Code  

• AWS 4.8.0 (Upgrade to v4 guide)
• Azure 3.0.2 (Upgrade to 3.0 guide)
• Google 4.15.0
• Scaleway 2.2.0

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.

• 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. 

• A common resource shared between multiple architecture
• For security reason (read-only access)
• Managed by another team