Configuration

Environments in Facets represent distinct deployment destinations for your cloud architecture blueprints. Each environment can have its own specific configurations, allowing you to maintain consistent infrastructure while accommodating different requirements across development, testing, and production deployments.

Configuration Overrides

Facets allows you to customize configurations for each environment through overrides. This feature enables you to:

• Modify resource configurations at the environment level without changing the blueprint
• Manage environment-specific variables
• Maintain blueprint integrity while supporting environment-specific customisation need.

---

Types of Environment Configurations

Resource Configurations

Resource configurations set at the project level serve as defaults and can be overridden at the environment level when needed. Any environment-level override takes precedence over the project default during deployment.

Environment Variables

Define environment-specific operational parameters:

• Service URLs (production CDN vs development asset server)
• Feature flags (enable beta features in development only)
• Logging levels (DEBUG for development, INFO for production)
• Cache settings (cache sizes, TTL values)

Secrets Management

Manage sensitive data separately for each environment:

• Database credentials (production vs development database users)
• API keys (production API keys vs test API keys)
• Authentication tokens (production authentication services)
• Encryption keys (environment-specific encryption)
• Service account credentials (production service accounts vs test accounts)