Aspire Azure Storage fails with The template output 'dataLakeEndpoint' is not valid
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 991
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 196
Description
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Describe the bug
Hello,
During Azure deployment, it fails with the following error:
'Failed to provision medico-storage: Deployment failed: Error code = DeploymentOutputEvaluationFailed, Message = The
template output 'dataLakeEndpoint' is not valid: The language expression property 'dfs' doesn't exist, available properties are 'web, blob'..
The storage was added with the following code in AppHost:
`var storage = builder.AddAzureStorage("storage")
.ConfigureInfrastructure(infra =>
{
var storageAccount = infra.GetProvisionableResources()
.OfType()
.Single();
storageAccount.Sku = new StorageSku { Name = StorageSkuName.PremiumLrs };
storageAccount.AccessTier = StorageAccountAccessTier.Hot;
storageAccount.Tags.Add("environment", "production");
});`
Have not found nothing online about this issue and also I have tried to make a fresh deploy in it's own Resource Group.
### Expected Behavior
The deployment should of completed succesfully without any errors.
### Steps To Reproduce
Create a simple Aspire App and add a Azure Storage with a Blob and reference it in a few APIs. Then just try to deploy to Azure Noth Europe.
### Exceptions (if any)
_No response_
### Aspire doctor output
Failed to provision medico-storage: Deployment failed: Error code = DeploymentOutputEvaluationFailed, Message = The
template output 'dataLakeEndpoint' is not valid: The language expression property 'dfs' doesn't exist, available properties are 'web, blob'.. (8.2s)
### Anything else?
_No response_
Contributor guide
Research direction
Start with the AppHost Azure Storage resource configured through AddAzureStorage and reproduce the deployment in a simple Aspire app targeting Azure North Europe. Trace the generated deployment template output named dataLakeEndpoint and compare it with the storage account properties reported in the error. Done means the storage deployment completes successfully without the invalid dfs expression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100