Labraboard: The Intelligent IaC Management Platform

About Labraboard

Labraboard is a state-aware Infrastructure as Code (IaC) platform specifically designed to manage Terraform configurations with ease and efficiency. Inspired by the Labrador, a versatile and intelligent working dog known for its roles as a guide, rescuer, and retriever, Labraboard embodies these qualities by becoming an indispensable tool in your infrastructure management toolkit.

Key Features

• State Management: Efficiently handle Terraform states with support for InMemory storage, HTTP backend, PostgreSQL backend, and Redis queue.
• Lock Handling: Robust mechanisms to handle state locks, ensuring smooth and safe infrastructure updates.
• Custom Environment and Variables: Tailor your Terraform and OpenTofu environments with custom configurations for seamless deployments.
• Dynamic Backend Configuration: Automatically override backend configurations during plan or apply operations, simplifying the setup process.
• Project Operations: Manage projects with create, read, update, and delete functionalities, including the ability to specify Git references, set default values, and configure other essential parameters.
• Time Lease for State: Implement time-based leases to manage state longevity.
• User Configuration: Customize user settings and preferences.

Why Labraboard?

Terraform is a powerful tool for managing infrastructure, but handling governance and surrounding processes can be challenging. Labraboard addresses these challenges, making it easier to run plans and apply infrastructure changes efficiently. With Labraboard, you can focus on building and deploying your infrastructure without worrying about the complexities of governance.

Labraboard - inspired by the intelligence and versatility of a Labrador, is here to be your guide in the world of infrastructure management.

Demo

if it is too fast there is a slower bit version: link

.HTTP files

You can try by own this tool using app.rest file please bear aware that you have to change values in file http-client.env.json and add a private value ARM_CLIENT_SECRET for azure. I enhance you to test in your terraform and your env variables :)

Starting point

Swagger docs has to be updated to reflect the new endpoints. It can be done by using command line swag init -g ./cmd/api/main.go -o ./docs

Swagger Page

Swagger API link

Upps here should be demo video - no worry, I will be soon! - Now check the API on https://api.labraboard.dev

Checking changes

git log --pretty=format:"%h%x09%an%x09%ad%x09%s"

RoadMap list

• Reading plan
• InMemory storage
• Trigger run plan
• Override backend
• Use custom Env and variables on to terraform
• Http Backend (Get Put)
• Handle Locks on the state
• Handle Destroy
• Add PostgreSQL as backend
• Redis queue
• Project CRUD
• Add reference to git sha in aggregate and relate with plans
• Add mapping to decouple mapping between aggregates and repository
• Add and remove env variables
• Add and remove variables
• Fix handling returning changes from plan
• Add unit testing of aggregates
• Bug fixing e2e testing (manually)
• Path for parameters in git folder
• Create handlers cmd
• Time Lease for the state
• Refactor and move to use interfaces in handlers
• Implement Logging
  • Logger and move init code to init function
  • Integrate logger with gin - use middleware for recordId, in future userId
  • Propagate context values between loggers
  • Replace all print to logger
  • Add every method ctx to enrich logger
  • Integrate handlers to use logger
• Handle scheduled plan in TerraformPlanner
• Run plan using http backend
• Access Token for Backend http
• Clean solution to be more DDD
• Create Plan changes during run, what was happened during the time
• Apply Mechanism to handle the state
  • Apply based on the Plan
  • Save outputs as deployment, handle errors
• Backup before apply using ApplyOptions.Backup
• Implement retries on apply
• Correlate Project, Deployment, Plans
• Integrate with the Git
• Handle other version than version 4.0 of tf
• Handle multiple version of tf and tofu
• Policies and run on pre/post plan/apply
• Authenticate
• User configuration
• Add a web interface
• Encryption at rest

Http Backend

Solution uses own delivered http backend where state is kept. During running plan or apply the backend configuration is added automatically by overriding the backend.

Example of using own http Backend

please use your project id. Application use it identify terraform state.

terraform {
  backend "http" {
    address = "http://localhost:8080/api/v1/state/terraform/bee3cf56-ecd1-4434-8e18-02b0ae2950cc"
    lock_address = "http://localhost:8080/api/v1/state/terraform/bee3cf56-ecd1-4434-8e18-02b0ae2950cc/lock"
    unlock_address = "http://localhost:8080/api/v1/state/terraform/bee3cf56-ecd1-4434-8e18-02b0ae2950cc/lock"
  }
}

Disclaimer

Please note that this project is currently under active development and is not considered production-ready. We are continuously working to improve and stabilize its features, but it does not yet meet all the requirements for production use.