Manage Environments

Manage existing environments (collections) in Bluebricks. The bricks collection commands operate on collections -- the platform's logical unit for organizing cloud infrastructure.

Prerequisites

• Bluebricks CLI installed

• Authenticated with Bluebricks (bricks login)

• Existing environments (collections)

Environment Commands

Listing Environments

# List active environments
bricks collection ls

# List all environments (including inactive)
bricks collection ls --all

Environment Information

The bricks collection ls command displays:

• GUID: Environment unique identifier

• NAME: Environment display name

• CLOUD PROVIDER: Connected cloud provider (AWS, GCP, Azure)

• CLOUD ACCOUNT: Connected cloud account name

• SLUG: Environment slug for commands

• STATUS: Environment status and latest deployment

Enabling Environments

# Enable by slug
bricks collection enable --slug "my-environment"

# Enable by ID
bricks collection enable --id "env-uuid-here"

Disabling Environments

# Disable with confirmation prompt
bricks collection disable --slug "my-environment"

# Disable without confirmation
bricks collection disable --slug "my-environment" --y

# Disable by ID
bricks collection disable --id "env-uuid-here"

Deleting Environments

# Delete environment by slug
bricks collection delete --slug "my-environment"

Environment Status

Status Indicators

• DEFAULT: Environment is set as default

• INACTIVE: Environment is disabled

• Latest Deployment: Shows most recent deployment name and stage

Collection States

State	Description	Action Required
Active	Collection is enabled	Ready for deployments
Inactive	Collection is disabled	Enable before use
Default	Collection is the default target	Used when no --collection is specified

Environment Management

Setting Default Environment

# Create environment as default
bricks collection create --name "development" --default

# Note: There's no direct command to change default after creation

Environment Organization

# List all environments
bricks collection ls --all

# Check environment status
bricks collection ls

Environment Cleanup

# Disable unused environment
bricks collection disable --slug "old-environment" --y

# Delete environment
bricks collection delete --slug "old-environment"

Environment Examples

Development Workflow

# List environments
bricks collection ls

# Enable development environment
bricks collection enable --slug "development"

# Deploy to development
bricks install @bluebricks/postgres@1.0.0 --collectiondevelopment

Production Management

# List all environments
bricks collection ls --all

# Enable production environment
bricks collection enable --slug "production"

# Deploy to production
bricks install @bluebricks/postgres@1.0.0 --collectionproduction

Environment Maintenance

# Disable staging environment
bricks collection disable --slug "staging"

# Delete old environment
bricks collection delete --slug "old-staging"

Best Practices

Regular Maintenance

• Review the environment list regularly

• Disable unused collections

• Delete collections when no longer needed

Collection Organization

• Use descriptive names

• Keep production collections separate

• Use the default environment for development

Access Control

• Monitor collection access via RBAC

• Use appropriate permissions

• Review collection status regularly

See also

• Collections -- what collections contain, policies, and RBAC

• How to Create Environments -- create new environments via CLI

• Environment Cloud Connection -- connect cloud accounts