setup default recipe pack for rad init, rad env commands and rad deploy env.bicep by nithyatsu · Pull Request #11212 · radius-project/radius

nithyatsu · 2026-02-10T15:54:29Z

Description

rad init

uses Radius.Core API
creates singleton recipe packs in the default resource group scope (not the workspace scope) and links their IDs to the

rad env create --preview

adds recipe packs when creating a new Radius.Core environment, automatically creates singleton recipe packs in the default scope (if needed) and attaches them to the environment.

rad env update

on update, inspects existing recipe packs on the environment, detects conflicts, and ensures any missing singletons are created (as needed in default scope) and linked. conflicts are reported.

rad deploy

before deploying, scans the compiled ARM template for all Radius.Core/environments.
For each environment found, inspects existing recipe packs, checks for conflicts, creates (as needed) missing singletons in the default scope, and injects their IDs into the template's .properties.recipePacks so the environment is deployed with full recipe pack coverage.

Type of change

This pull request fixes a bug in Radius and has an approved issue (issue link required).
This pull request adds or changes features of Radius and has an approved issue (issue link required).
This pull request is a minor refactor, code cleanup, test improvement, or other maintenance task and doesn't change the functionality of Radius (issue link optional).

Fixes: #11091

Contributor checklist

Please verify that the PR meets the following requirements, where applicable:

An overview of proposed schema changes is included in a linked GitHub issue.
- Yes
- Not applicable
A design document PR is created in the design-notes repository, if new APIs are being introduced.
- Yes
- Not applicable
The design document has been reviewed and approved by Radius maintainers/approvers.
- Yes
- Not applicable
A PR for the samples repository is created, if existing samples are affected by the changes in this PR.
- Yes
- Not applicable
A PR for the documentation repository is created, if the changes in this PR affect the documentation or any user facing updates are made.
- Yes
- Not applicable
A PR for the recipes repository is created, if existing recipes are affected by the changes in this PR.
- Yes
- Not applicable

radius-functional-tests · 2026-02-11T04:00:32Z

Radius functional test overview

🔍 Go to test action run

Click here to see the test run details

Name	Value
Repository	nithyatsu/radius
Commit ref	`b684d7a`
Unique ID	funce49674cc7f
Image tag	pr-funce49674cc7f

gotestsum 1.13.0
KinD: v0.29.0
Dapr: 1.14.4
Azure KeyVault CSI driver: 1.4.2
Azure Workload identity webhook: 1.3.0
Bicep recipe location ghcr.io/radius-project/dev/test/testrecipes/test-bicep-recipes/<name>:pr-funce49674cc7f
Terraform recipe location http://tf-module-server.radius-test-tf-module-server.svc.cluster.local/<name>.zip (in cluster)
applications-rp test image location: ghcr.io/radius-project/dev/applications-rp:pr-funce49674cc7f
dynamic-rp test image location: ghcr.io/radius-project/dev/dynamic-rp:pr-funce49674cc7f
controller test image location: ghcr.io/radius-project/dev/controller:pr-funce49674cc7f
ucp test image location: ghcr.io/radius-project/dev/ucpd:pr-funce49674cc7f
deployment-engine test image location: ghcr.io/radius-project/deployment-engine:latest

Test Status

⌛ Building Radius and pushing container images for functional tests...
✅ Container images build succeeded
⌛ Publishing Bicep Recipes for functional tests...
✅ Recipe publishing succeeded
⌛ Starting corerp-cloud functional tests...
⌛ Starting ucp-cloud functional tests...
✅ ucp-cloud functional tests succeeded
✅ corerp-cloud functional tests succeeded

Copilot

Pull request overview

Updates the Radius CLI to ensure default (singleton) recipe packs exist in the fixed default scope and are linked automatically during rad init, rad env create/update (preview), and rad deploy when deploying Radius.Core/environments.

Changes:

Introduces pkg/cli/recipepack utilities for creating/inspecting singleton recipe packs and detecting conflicts.
Updates CLI flows (rad init, rad env create/update --preview, rad deploy) to create missing singleton packs in /planes/radius/local/resourceGroups/default and attach/inject their IDs.
Extends Radius.Core test client fakes and adds unit tests around recipe pack inspection/injection behavior.

Reviewed changes

Copilot reviewed 18 out of 18 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
test/functional-portable/cli/noncloud/testdata/corerp-recipe-pack-test.bicep	Updates functional test recipe pack contents.
test/functional-portable/cli/noncloud/cli_test.go	Removes dev-recipe functional test that directly called `radinit` internals.
pkg/cli/test_client_factory/radius_core.go	Adds fake server behaviors for env/recipe pack create/update and conflict simulation.
pkg/cli/recipepack/recipepack.go	New shared recipe pack/singleton utilities used across commands.
pkg/cli/recipepack/recipepack_test.go	New unit tests for recipe pack utilities (coverage/conflicts/extraction).
pkg/cli/cmd/utils.go	Adds `PopulateRecipePackClients` helper for multi-scope recipe pack inspection.
pkg/cli/cmd/utils_test.go	Adds tests for `PopulateRecipePackClients`.
pkg/cli/cmd/radinit/options.go / options_test.go	Switches workspace environment IDs to `Radius.Core/environments`.
pkg/cli/cmd/radinit/init.go / init_test.go	Wires Radius.Core client factories into `rad init` tests and expectations.
pkg/cli/cmd/radinit/environment.go	Creates Radius.Core environments and links singleton recipe packs in default scope.
pkg/cli/cmd/env/create/preview/create.go / create_test.go	Creates environments with default-scope singleton recipe packs (preview).
pkg/cli/cmd/env/update/preview/update.go / update_test.go	Inspects packs, detects conflicts, ensures missing singletons (preview).
pkg/cli/cmd/deploy/deploy.go / deploy_test.go	Injects missing singleton recipe pack IDs into templates before deploy.

Copilot · 2026-02-13T00:03:32Z

pkg/cli/recipepack/recipepack.go

+// 		if err != nil {
+// 			return nil, fmt.Errorf("failed to get recipe pack %q: %w", name, err)
+// 		}
+// 		if resp.Properties != nil && resp.Properties.Recipes != nil {
+// 			for resourceType := range resp.Properties.Recipes {
+// 				typeToPackNames[resourceType] = append(typeToPackNames[resourceType], name)
+// 			}
+// 		}
+// 	}
+// 	conflicts := make(map[string][]string)
+// 	for resourceType, packs := range typeToPackNames {
+// 		if len(packs) > 1 {
+// 			conflicts[resourceType] = packs
+// 		}
+// 	}
+// 	return conflicts, nil
+// }
+


pkg/cli/recipepack/recipepack.go contains large blocks of commented-out, duplicate implementations (CollectResourceTypesFromRecipePacks / DetectResourceTypeConflicts). This dead code makes the new package harder to maintain and risks divergence from the real implementations; delete these blocks if they’re no longer needed or move them to version control history/docs.

Suggested change

// if err != nil {

// return nil, fmt.Errorf("failed to get recipe pack %q: %w", name, err)

// }

// if resp.Properties != nil && resp.Properties.Recipes != nil {

// for resourceType := range resp.Properties.Recipes {

// typeToPackNames[resourceType] = append(typeToPackNames[resourceType], name)

// }

// }

// }

// conflicts := make(map[string][]string)

// for resourceType, packs := range typeToPackNames {

// if len(packs) > 1 {

// conflicts[resourceType] = packs

// }

// }

// return conflicts, nil

// }

Copilot · 2026-02-13T00:03:32Z

pkg/cli/cmd/deploy/deploy.go

+
+		// Extract symbolic name from patterns like:
+		//   [reference('mypack').id]
+		//   [resourceId('Radius.Core/recipePacks', 'name')]


findReferencedRecipePackNames()’s comment mentions parsing [resourceId('Radius.Core/recipePacks', 'name')], but extractSymbolicNameFromExpression() only handles reference('...') expressions. Either implement resourceId parsing or remove it from the comment to avoid misleading future changes.

Suggested change

// [resourceId('Radius.Core/recipePacks', 'name')]

Copilot · 2026-02-13T00:03:32Z

pkg/cli/cmd/utils.go

+	for _, packIDStr := range packIDs {
+		// This is the bicep reference for id, and cannot be invalid.
+		packID, _ := resources.Parse(packIDStr)
+		scope := packID.RootScope()
+		if _, exists := clientsByScope[scope]; exists {
+			continue
+		}


PopulateRecipePackClients ignores errors from resources.Parse. If packIDs contains an invalid ID (or an ARM expression that slipped through), Parse will return an error and packID.RootScope() will default to "/", causing an incorrect client to be created (or overwriting clientsByScope["/"]). Handle the error (skip invalid IDs like InspectRecipePacks does, or return a validation error) instead of discarding it.

Copilot · 2026-02-13T00:03:33Z

pkg/cli/cmd/utils_test.go

+	t.Run("no-op for empty packIDs", func(t *testing.T) {
+		clientsByScope := map[string]*v20250801preview.RecipePacksClient{
+			scope: {}, // placeholder client
+		}
+
+		err := PopulateRecipePackClients(context.Background(), &workspaces.Workspace{Scope: scope}, clientsByScope, nil)
+		require.NoError(t, err)
+		require.Len(t, clientsByScope, 1)
+	})
+
+	t.Run("skips packs whose scope is already in the map", func(t *testing.T) {
+		clientsByScope := map[string]*v20250801preview.RecipePacksClient{
+			scope: {},
+		}


The test initializes a map[string]*RecipePacksClient with scope: {}. {} is not a valid value for a pointer type and will not compile; use &v20250801preview.RecipePacksClient{} (or another non-nil placeholder) instead.

Copilot · 2026-02-13T00:03:33Z

pkg/cli/cmd/deploy/deploy.go

+		if _, exists := coveredTypes[resourceType]; !exists {
+			coveredTypes[resourceType] = packName
+		}


When merging resource-type coverage from template-defined recipe packs (ARM expression references), conflicts are not detected if a resource type is already covered by a literal pack (or by another template-defined pack). This can allow environments to be deployed with two packs providing the same resource type without raising a conflict. Track pack lists per resource type for both sources and surface conflicts consistently.

Suggested change

if _, exists := coveredTypes[resourceType]; !exists {

coveredTypes[resourceType] = packName

}

if existingPack, exists := coveredTypes[resourceType]; exists {

if existingPack != packName {

return fmt.Errorf("resource type %q is provided by multiple recipe packs: %q and %q", resourceType, existingPack, packName)

}

}

coveredTypes[resourceType] = packName

Copilot · 2026-02-13T00:03:33Z

pkg/cli/cmd/env/create/preview/create.go

+// Run implements create-or-update semantics. If the environment does not exist, it creates
+// a new one with all singleton recipe packs for core resource types. If the environment
+// already exists, it checks the existing recipe packs and fills in any missing singletons
+// for core resource types, detecting conflicts along the way.


The Run() doc comment says this command “checks the existing recipe packs … detecting conflicts”, but the implementation always calls runCreate(), which unconditionally sets RecipePacks to the singleton set and does not inspect existing environment state. Update the comment to match current behavior or implement the described create-or-update/conflict logic.

Suggested change

// Run implements create-or-update semantics. If the environment does not exist, it creates

// a new one with all singleton recipe packs for core resource types. If the environment

// already exists, it checks the existing recipe packs and fills in any missing singletons

// for core resource types, detecting conflicts along the way.

// Run creates a new environment with all singleton recipe packs for core resource types.

// It does not inspect existing environment state or perform conflict detection.

Signed-off-by: nithyatsu <nithyasu@microsoft.com>

Signed-off-by: nithyatsu <nithyasu@microsoft.com> rad init implementation Signed-off-by: nithyatsu <nithyasu@microsoft.com> name default pack Signed-off-by: nithyatsu <nithyasu@microsoft.com> add tests Signed-off-by: nithyatsu <nithyasu@microsoft.com> wip Signed-off-by: nithyatsu <nithyasu@microsoft.com> rad init cahnges Signed-off-by: nithyatsu <nithyasu@microsoft.com> wip Signed-off-by: nithyatsu <nithyasu@microsoft.com> wip Signed-off-by: nithyatsu <nithyasu@microsoft.com> wip Signed-off-by: nithyatsu <nithyasu@microsoft.com> renames Signed-off-by: nithyatsu <nithyasu@microsoft.com> create upadtes Signed-off-by: nithyatsu <nithyasu@microsoft.com> update Signed-off-by: nithyatsu <nithyasu@microsoft.com> wip Signed-off-by: nithyatsu <nithyasu@microsoft.com> deploy changes Signed-off-by: nithyatsu <nithyasu@microsoft.com> wip Signed-off-by: nithyatsu <nithyasu@microsoft.com> wip Signed-off-by: nithyatsu <nithyasu@microsoft.com> wip Signed-off-by: nithyatsu <nithyasu@microsoft.com> refactor + comments Signed-off-by: nithyatsu <nithyasu@microsoft.com> deploy fix Signed-off-by: nithyatsu <nithyasu@microsoft.com> fix Signed-off-by: nithyatsu <nithyasu@microsoft.com> remove dev recipe test Signed-off-by: nithyatsu <nithyasu@microsoft.com> wip Signed-off-by: nithyatsu <nithyasu@microsoft.com> ci: retrigger ci: retrigger ci: retrigger

Signed-off-by: nithyatsu <nithyasu@microsoft.com>

nithyatsu requested a deployment to external-contributor-approval February 10, 2026 15:54 — with GitHub Actions Waiting

nithyatsu changed the title ~~Setupkubepackdeploy~~ setup default recipe pack for rad init, rad env commands and rad deploy env.bicep Feb 10, 2026

nithyatsu temporarily deployed to external-contributor-approval February 10, 2026 18:41 — with GitHub Actions Inactive

nithyatsu marked this pull request as ready for review February 10, 2026 18:42

nithyatsu requested review from a team as code owners February 10, 2026 18:42

nithyatsu force-pushed the setupkubepackdeploy branch from 4a5c293 to 336a085 Compare February 10, 2026 19:07

nithyatsu requested a deployment to external-contributor-approval February 10, 2026 19:08 — with GitHub Actions Waiting

nithyatsu temporarily deployed to publish-bicep February 10, 2026 19:08 — with GitHub Actions Inactive

nithyatsu temporarily deployed to publish-bicep February 10, 2026 19:31 — with GitHub Actions Inactive

nithyatsu temporarily deployed to external-contributor-approval February 10, 2026 19:32 — with GitHub Actions Inactive

nithyatsu temporarily deployed to external-contributor-approval February 10, 2026 19:36 — with GitHub Actions Inactive

nithyatsu temporarily deployed to publish-bicep February 10, 2026 19:37 — with GitHub Actions Inactive

nithyatsu temporarily deployed to external-contributor-approval February 10, 2026 20:26 — with GitHub Actions Inactive

nithyatsu temporarily deployed to publish-bicep February 10, 2026 20:26 — with GitHub Actions Inactive

nithyatsu force-pushed the setupkubepackdeploy branch from caf2a8f to 2d515c0 Compare February 10, 2026 21:12

nithyatsu temporarily deployed to external-contributor-approval February 10, 2026 21:12 — with GitHub Actions Inactive

nithyatsu temporarily deployed to publish-bicep February 10, 2026 21:12 — with GitHub Actions Inactive

nithyatsu temporarily deployed to external-contributor-approval February 10, 2026 21:16 — with GitHub Actions Inactive

nithyatsu temporarily deployed to publish-bicep February 10, 2026 21:17 — with GitHub Actions Inactive

nithyatsu temporarily deployed to external-contributor-approval February 10, 2026 21:31 — with GitHub Actions Inactive

nithyatsu temporarily deployed to publish-bicep February 10, 2026 21:31 — with GitHub Actions Inactive

nithyatsu temporarily deployed to external-contributor-approval February 10, 2026 22:00 — with GitHub Actions Inactive

nithyatsu temporarily deployed to publish-bicep February 10, 2026 22:00 — with GitHub Actions Inactive

nithyatsu temporarily deployed to external-contributor-approval February 11, 2026 03:56 — with GitHub Actions Inactive

nithyatsu temporarily deployed to publish-bicep February 11, 2026 03:56 — with GitHub Actions Inactive

nithyatsu requested a review from kachawla February 12, 2026 22:33

kachawla requested a review from Copilot February 12, 2026 23:54

Copilot started reviewing on behalf of kachawla February 12, 2026 23:54 View session

Copilot AI reviewed Feb 13, 2026

View reviewed changes

nithyatsu mentioned this pull request Feb 18, 2026

Default Recipe Packs for K8s #11074

Open

nithyatsu marked this pull request as draft February 19, 2026 19:04

nithyatsu added 12 commits February 19, 2026 14:13

update rad install

f2df685

Signed-off-by: nithyatsu <nithyasu@microsoft.com>

check default rg

d840624

Signed-off-by: nithyatsu <nithyasu@microsoft.com>

wip

9223013

Signed-off-by: nithyatsu <nithyasu@microsoft.com>

update tests

564ba8c

Signed-off-by: nithyatsu <nithyasu@microsoft.com>

wip

1598680

Signed-off-by: nithyatsu <nithyasu@microsoft.com>

refactor

29acb03

Signed-off-by: nithyatsu <nithyasu@microsoft.com>

fix for recipepack reference from template

12eb9dd

Signed-off-by: nithyatsu <nithyasu@microsoft.com>

Update rad init

fb1e47a

Signed-off-by: nithyatsu <nithyasu@microsoft.com>

remove changes to update

3d0d0cb

Signed-off-by: nithyatsu <nithyasu@microsoft.com>

rad init updates

c0e374e

Signed-off-by: nithyatsu <nithyasu@microsoft.com>

update env create

0124690

Signed-off-by: nithyatsu <nithyasu@microsoft.com>

nithyatsu force-pushed the setupkubepackdeploy branch from b684d7a to 0124690 Compare February 19, 2026 23:39

nithyatsu requested a deployment to external-contributor-approval February 19, 2026 23:39 — with GitHub Actions Waiting

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Comments

setup default recipe pack for rad init, rad env commands and rad deploy env.bicep#11212

setup default recipe pack for rad init, rad env commands and rad deploy env.bicep#11212
nithyatsu wants to merge 12 commits intoradius-project:mainfrom
nithyatsu:setupkubepackdeploy

nithyatsu commented Feb 10, 2026 •

edited

Loading

Uh oh!

radius-functional-tests bot commented Feb 11, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Comments

Conversation

nithyatsu commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Type of change

Contributor checklist

Uh oh!

radius-functional-tests bot commented Feb 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Radius functional test overview

Test Status

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

nithyatsu commented Feb 10, 2026 •

edited

Loading

radius-functional-tests bot commented Feb 11, 2026 •

edited

Loading