RadiusInfrastructureOptions Properties
ConfigureRadiusInfrastructure callback. Radius.Core/applications constructs. public List<RadiusApplicationConstruct> Applications { get; }Radius.Compute/containers workload constructs. public List<RadiusContainerConstruct> Containers { get; }Radius.Core/environments constructs. public List<RadiusEnvironmentConstruct> Environments { get; }Applications.Core/applications constructs paired with RadiusInfrastructureOptions.LegacyEnvironments . public List<LegacyApplicationConstruct> LegacyApplications { get; }Applications.Core/environments constructs emitted when one or more targeted resources fall back to a legacy Applications.* type (e.g., Mongo, SQL Server, Dapr). public List<LegacyApplicationEnvironmentConstruct> LegacyEnvironments { get; }@secure() so their values are supplied at deploy time via rad deploy --parameters rather than inlined. public List<ProvisioningParameter> Parameters { get; }Radius.Core/recipePacks constructs. public List<RadiusRecipePackConstruct> RecipePacks { get; }Radius.Data/redisCaches , Radius.Messaging/rabbitMQ ). public List<RadiusResourceTypeConstruct> ResourceTypeInstances { get; }Applications.Core/secretStores constructs emitted for the Radius secret stores declared via AddRadiusSecretStore / WithSecretStore . public List<RadiusSecretStoreConstruct> SecretStores { get; }Radius.Security/secrets constructs — the Radius.* UDT secret primitive. The collection holds two kinds of entry, both of which a callback can observe: public List<RadiusSecuritySecretConstruct> SecuritySecrets { get; }Remarks
The first kind carries a credential a UDT backing resource consumes by resource ID (for example the RabbitMQ properties.). The second is generated per container to back its credential-bearing environment variables: a variable whose value carries a secret is emitted as a value into a secret named after the container (for example api-) rather than as a literal value, which is what keeps the credential out of the Deployment spec and its rollout history. Both kinds are ordinary Radius. resources, so nothing distinguishes them structurally — a callback that treats every entry here as backing-resource state and removes one may be removing the secret a container reads from.
Removing a container's secret, or the data key an environment variable names, is rejected with ASPIRERADIUS084 rather than silently emitted, because the resulting artifact is accepted by Radius and only fails as a pod that never starts. Set the environment variable explicitly in the callback if the intent is to supply the value another way.
Exposed for the same reason as the other collections: Configure can rename a construct, and callers that rename one of these must be able to see it. The publisher repairs the consuming resource's ID reference — and a container's secret, which names the secret by resource name — after the callbacks run, so a rename of either kind does not dangle.
Aspire