Environments

Introduction

This section provides a technical reference for configuring Management and Operational Environments using the Fractal Cloud SDK. You'll find detailed information about the properties and options available for each environment type.

Management Environment

Management Environments serve as the central point of control for your Fractal Cloud resources. They allow you to manage cloud agents, secrets, CI/CD profiles, and other settings that apply across your operational environments.

name

string

resourceGroups

Collection<UUID>

Required

tags

Map<String, String>

secrets

Collection<Secret>

defaultCiCdProfile

CiCdProfile

ciCdProfiles

Collection<CiCdProfile>

id

EnvironmentIdValue

Required

operationalEnvironments

Collection<OperationalEnvironment>

withAwsCloudAgent

AwsCloudAgent

withAzureCloudAgent

(region: AzureRegion, tenantId: UUID, subscriptionId: UUID) => ManagementEnvironmentBuilder

withGcpCloudAgent

(region: GcpRegion, organizationId: string, projectId: string) => ManagementEnvironmentBuilder

withOciCloudAgent

(region: OciRegion, tenancyId: string, compartmentId: string) => ManagementEnvironmentBuilder

Operational Environment

Operational Environments represent the specific cloud environments where your applications and workloads are deployed. They allow you to configure region-specific details, including secrets and CI/CD profiles.

name

string

resourceGroups

Collection<UUID>

Required

tags

Map<String, String>

secrets

Collection<Secret>

defaultCiCdProfile

CiCdProfile

ciCdProfiles

Collection<CiCdProfile>

shortName

string

Required

withAwsAccount

(region: AwsRegion, accountId: string) => OperationalEnvironmentBuilder

withAzureSubscription

(region: AzureRegion, subscriptionId: UUID) => OperationalEnvironmentBuilder

withGcpProject

(region: GcpRegion, projectId: string) => OperationalEnvironmentBuilder

withOciCompartment

(region: OciRegion, compartmentId: string) => OperationalEnvironmentBuilder

Secrets and CI/CD Profiles in Operational Environments

You can define secrets and CI/CD profiles directly within an Operational Environment. This allows you to:

• Provide environment-specific configurations: For example, you might have different database credentials or API keys for your staging and production environments.

Important

Secrets and CI/CD profiles must be defined on the environment that is used by your LiveSystem. This ensures that your workloads have access to the necessary credentials and deployment configurations.