Brainboard's documentation
Go to the app ↗
  • Welcome
  • Getting started
    • Fast track
    • Start with a template
    • Start with AI
    • Use cases videos
    • Brainboard philosophy
  • Cloud design
    • Left bar
      • Cloud resources
      • Input & output
    • Design area
      • Node
      • ID card
      • Connectors
      • Versioning
      • Graphical options
    • One action
    • Code Edition
  • Data
    • Data structure
      • Project
      • Environment
      • Cloud architecture
        • Terraform files
        • Readme file
        • Architecture Synchronization
        • Remote backend
      • Template
    • Cloud providers
      • Supported cloud providers
      • Customize provider configuration
      • Unsupported cloud providers
    • Terraform / OpenTofu
      • Modules
        • Module
        • Import modules
        • Manage module
        • Terraform registry credentials
        • Use modules
    • Disaster recovery
  • Automation
    • CI/CD engine
    • Supported plugins
      • Terraform
      • Security
        • Trivy
        • Tfsec
        • Terrascan
        • OPA
        • Checkov
      • Infracost
      • Notifications
        • Email
        • Slack
        • Microsoft Teams
      • Webhooks
    • Pipelines
    • Workflow templates
    • Drift detection
      • Types of drift
      • Remediation
    • Self-Hosted Runner
      • Deploy runner with Kubernetes
      • Deploy runner with docker-compose
  • Settings
    • Overview
    • Authentication
      • Login into Brainboard
      • Single sign-on (SSO)
    • Account management
    • Organization
    • Members
    • Teams
    • Roles & Permissions (RBAC)
      • Level of access
      • Organization RBAC
      • Project RBAC
    • Integrations
      • Git configuration
        • GitHub
        • Azure DevOps (ADO)
        • Bitbucket
        • GitLab
        • How to use
      • Cloud providers
        • AWS
        • Azure
        • GCP
        • OCI
  • Security
    • Data managed by Brainboard
    • SOC 2 Type II
    • Role Based Access Control
  • Help & FAQ
    • Shortcuts
    • FAQ
    • Migration
      • Import from cloud provider
    • Support
    • Glossary
  • Changelog
Powered by GitBook
On this page
  • Description
  • Create a new environment
  • Update environment
  • Delete environment
  • Synchronize architectures across environments

Was this helpful?

Edit on GitHub
  1. Data
  2. Data structure

Environment

PreviousProjectNextCloud architecture

Last updated 6 months ago

Was this helpful?

Description

An environment is a logical grouping of cloud architectures that are supposed to have the same criticality or serve the same purpose. Like dev, staging, QA, prod…

Environments can be used to separate and isolate development, staging, and production resources, or to create dedicated environments for different teams or applications.

Brainboard environments provide a flexible and powerful way to manage your cloud infrastructure. It is like a folder, you can put any logic that reflects your processes.

Create a new environment

  • To create a new environment, click on the name of the architecture in the top-left corner to open the projects' page, and click on the + as below :

Update environment

To update an existing environment, first click on the name of the environment, it will select it and display the following information on the right that you can customize:

  1. Environment name.

  2. Description: Multiline description of your environment.

  3. Tags: You can add multiple tags. These tags are searchable.

  4. Read-only information:

    1. Updated at: When the last time the environment has been updated. UTC timezone.

    2. Created at: When the projected has been created. UTC timezone.

    3. Updated by: Who is the last person who updated the environment.

    4. Created by: Who created the environment.

  5. ID: This is the environment UUID. You need it when you communicate with our support.

Delete environment

To delete an environment, click on it to select it, then click on delete button:

Deleting an environment will delete all architectures inside it. This action cannot be undone.

Synchronize architectures across environments

By following these steps, you can effectively manage multiple environments in Brainboard and ensure that your infrastructure is consistent and reliable across all stages. This is the best way to eliminate the drift between different environments.

Refer to the to know more about it.

Architecture Synchronization