AddRedis().WithDataVolume() generates storage account without minimum TLS 1.2 configuration

[vhvb1989]

Description

When using AddRedis().WithDataVolume(), the generated Azure Storage Account definition is missing the minimumTlsVersion: 'TLS1_2' property. This can trigger Azure security alerts and doesn't follow Azure security best practices.

Steps to Reproduce

1. Use the following code in an Aspire AppHost:

   var redis = builder.AddRedis("cache")
       .WithLifetime(ContainerLifetime.Persistent)
       .WithDataVolume();

2. Publish the application to generate Bicep templates

3. Examine the generated storage account resource definition

Expected Behavior

The generated storage account should include minimumTlsVersion: 'TLS1_2' to enforce secure connections and comply with Azure security best practices.

Actual Behavior

The storage account is generated without the minimumTlsVersion property, defaulting to potentially insecure TLS versions.

Environment

• Reproduction Location: playground/AzureContainerApps/AzureContainerApps.AppHost/Program.cs

Impact

• Triggers Azure security alerts
• Does not follow Azure security best practices
• Potential security compliance issues

[davidfowl]

This

aspire/src/Aspire.Hosting.Azure.AppContainers/AzureContainerAppExtensions.cs

Lines 175 to 181 in 694f646

	storageVolume = new StorageAccount(Infrastructure.NormalizeBicepIdentifier($"{appEnvResource.Name}_storageVolume"))
	{
	Tags = tags,
	Sku = new StorageSku() { Name = StorageSkuName.StandardLrs },
	Kind = StorageKind.StorageV2,
	LargeFileSharesState = LargeFileSharesState.Enabled
	};

[MihuBot]

I'm a bot. Here is a possible related and/or duplicate issue (I may be wrong):

• Azure Storage should provision with TLS 1.2 by default #4692