2025-08-01-preview on Radius Docs

Radius.Core/applications@2025-08-01-preview

Mon, 01 Jan 0001 00:00:00 +0000

Description

The Radius.Core/applications Resource Type represents a Radius Application: a logical grouping of the resources that make up a single Application, such as containers, databases, and message queues, along with the connections between them. Radius uses the Application to build the application graph, apply shared configuration, and manage its resources together throughout their lifecycle.

Defining an Application

An Application is always deployed to a Radius Environment, which is supplied through the environment property. To define an Application, add a Radius.Core/applications resource to your application definition Bicep file.

Radius.Core/bicepSettings@2025-08-01-preview

Mon, 01 Jan 0001 00:00:00 +0000

Description

The Radius.Core/bicepSettings Resource Type holds reusable Bicep engine settings that Environments apply when running Bicep Recipes. Its primary use is authenticating to private Bicep registries: OCI registries, such as Azure Container Registry, that host the Recipe templates referenced by a Recipe Pack.

Platform engineers define a Radius.Core/bicepSettings resource once and reference it from any Environment whose Recipes pull templates from a private registry.

Defining Bicep settings

Configure registryAuthentications, keyed by registry hostname. When a Recipe template is pulled from a matching host, Radius authenticates using the configured method. The example below uses basic authentication, reading the username and password from a secret:

Radius.Core/environments@2025-08-01-preview

Mon, 01 Jan 0001 00:00:00 +0000

Description

The Radius.Core/environments Resource Type represents a Radius Environment: the deployment target that platform engineers configure for their developers. Every Radius Application is deployed to an Environment through its environment property.

An Environment defines three things for the Applications deployed to it:

Where resources are deployed: the target compute platform and cloud provider accounts, set through the providers property.
Which Recipes are used: the Recipe Packs whose Recipes provision the infrastructure backing application resources, set through the recipePacks property.
Advanced Terraform and Bicep settings: environment-wide Recipe parameters and Terraform or Bicep engine configuration applied when Recipes run.

Defining an Environment

The simplest Environment can be created directly with the rad environment create command, without a Bicep file:

Radius.Core/recipePacks@2025-08-01-preview

Mon, 01 Jan 0001 00:00:00 +0000

Description

The Radius.Core/recipePacks Resource Type represents a Recipe Pack: a named collection of Recipes that platform engineers assign to an Environment. A Recipe maps a resource type (such as Radius.Data/redisCaches) to an infrastructure-as-code module, a Terraform module or Bicep template, that provisions the infrastructure backing that resource when a developer deploys it.

A Recipe Pack is defined as its own resource and referenced from an Environment’s recipePacks property, so one Recipe Pack can be shared across many Environments.

Radius.Core/terraformSettings@2025-08-01-preview

Mon, 01 Jan 0001 00:00:00 +0000

Description

The Radius.Core/terraformSettings Resource Type holds reusable Terraform CLI settings that Environments apply when running Terraform Recipes. Its primary use is authenticating to private Terraform registries that host the modules referenced by a Recipe Pack, along with configuring provider installation and injecting environment variables during Recipe execution.

Platform engineers define a Radius.Core/terraformSettings resource once and reference it from any Environment whose Recipes pull modules from a private registry.

Defining Terraform settings

Configure terraformrc.credentials, keyed by registry hostname, to authenticate to a private Terraform registry. Each entry points to a secret whose token key holds the registry token: