Repository navigation
radius@0.2.1
Patch Changes
-
#352 @zachcasper - Fixed: Keep the planned application graph and Radius type lookups working after the Azure Recipe Pack in
resource-types-contribmoved torecipe-packs/azure-aks/azure-aks.bicepand the Kubernetes pack torecipe-packs/kubernetes/default.bicep. Recipe lookups now use theazure-akspack entry from newer Radius releases and still fall back to theazureentry from older ones. -
#939 @nellshamrell - Fixed: Recover from eligible temporary workflow-read failures with bounded retries that respect GitHub's retry deadlines across polling, while retaining confirmed deployment and credential-verification outcomes when diagnostic evidence is unavailable. Resume artifact reads after timed cooldowns and release retired payloads during long deployments.
When a closed Canvas instance is physically stopped, Radius ends its local deployment monitoring and subsequent automatic repair handoff without cancelling the GitHub workflow. Monitoring continues during the existing deferred close for an active environment task.
-
#857 @nicolejms - Fixed: Show every resource listed in the delete confirmation without clipping the last entry or the remaining-count line. On macOS the list could outgrow its height limit and hide part of what the deletion would destroy behind a scrollbar that stays invisible until you interact with it.
-
#894 @kachawla - Security: Application model validation now fails when a Bicep credential-safety rule has been turned off instead of passing silently. A rule set to
offorinfoinbicepconfig.json, a disabled Bicep linter, or a#disable-next-lineor#disable-diagnosticsdirective naming one of these rules previously let a model with a hardcoded credential in a sensitive property validate cleanly. Validation now names the setting and the rule so it can be removed and the underlying problem fixed. This coversuse-secure-value-for-secure-inputs,secure-parameter-default,secure-secrets-in-params,outputs-should-not-contain-secrets, andsecure-params-in-nested-deploy. Settings for other rules inbicepconfig.jsonare still preserved. -
#893 @kachawla - Security: Pass Azure environment variables into the generated workflows' shell steps through the environment instead of substituting them into the script, so a value containing shell syntax is treated as data rather than as commands. No reconfiguration is needed; the same variables are read and resolve to the same values.
-
#926 @kachawla - Fixed: Deploy and delete workflows now install the Radius CLI and control plane from the pinned stable Radius release instead of the latest unreleased
edgebuild, so an unreleased Radius change can no longer break or change deployments. -
#907 @nellshamrell - Fixed: Preserve confirmed deployment outcomes when diagnostic logs or graph artifacts cannot be read, keep attributable deployment errors ahead of teardown errors, and avoid treating an unconfirmed workflow outcome as a confirmed failure.
Stop waiting when GitHub reports a completed workflow with an unsupported outcome. Report that the outcome could not be confirmed without suggesting the workflow is still running or starting automatic repair; missing outcomes retain their recovery window.
-
#915 @nellshamrell - Fixed: Reject conflicting deployment-artifact identities and unsafe status files, retire stale evidence even when another application's graph is malformed, and report malformed artifact listings as unavailable evidence rather than a missing deployment. Allow later reads to recover after an unexpected failure; bound malformed graph scanning and decoding while keeping valid progress readable even when a later graph cannot be recovered.
-
#888 @sk593 - Changed: Remove the transitional Azure recipe-pack compatibility shim now that the Radius defaults catalog points at the pack-only recipe pack. The Azure deploy workflow no longer probes the downloaded pack for the legacy
environmentName,environmentNamespace,azureSubscriptionId, andazureResourceGroupparameters, and passes only the parameters the pack-only artifact owns. Workflows already committed to a repository keep deploying unchanged and do not need to be regenerated: each loads the catalog its own pinned ref names, and the shim they still carry passes a legacy parameter only while the pack it downloads declares one. -
#927 @nicolejms - Fixed: Stop blocking pull request creation in worktrees that contain a Radius application model. Radius no longer requires an application graph diff before every pull request, no longer opens the graph-diff canvas after a pull request is created, and no longer tells the agent to generate a graph diff for unrelated pull requests. Ask for a graph diff explicitly when you want one.
-
#720 @AzureMike - Fixed: Select stable and exact release-candidate Radius Bicep types from the CLI's stamped release, allow edge's mutable latest types only for an executable
RADIUS_RAD_BINARYdeveloper override, and stop before modeling edge managed binaries or pull-request builds. Keep relative developer CLI paths usable when graph compilation changes working directories. -
#914 @nellshamrell - Fixed: Avoid immediately repeating failed workflow reads and retain a confirmed run outcome when job details are unavailable.