You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Output from azd version
Run azd version and copy and paste the output here:
azd version 1.7.0-beta.1-pr.3518885 (commit d62cc4c)
Describe the bug
Using .NET Aspire, when using an Azure Cosmos DB resource, an Azure Key Vault that is generated, the vault's name is too long.
I had this deployment error running azd up:
(✓) Done: Resource group: rg-codebreaker-12p4
(x) Failed: Key Vault: codebreakercosmoskvzehizmlsmqemc
(✓) Done: Log Analytics workspace: law-zehizmlsmqemc
(✓) Done: Log Analytics workspace: law-appinsights-zehizmlsmqemc
(✓) Done: Container Registry: acrzehizmlsmqemc
(✓) Done: Application Insights: appinsights-zehizmlsmqemc
(✓) Done: Container Apps Environment: cae-zehizmlsmqemc
(✓) Done: Container App: redis
ERROR: deployment failed: failing invoking action 'provision', error deploying infrastructure: deploying to subscription:
Deployment Error Details:
VaultNameNotValid: The vault name 'codebreakercosmoskvzehizmlsmqemc' is invalid. A vault's name must be between 3-24 alphanumeric characters. The name must begin with a letter, end with a letter or digit, and not contain consecutive hyphens. Follow this link for more information: https://go.microsoft.com/fwlink/?linkid=2147742
TraceID: c1ac58b6641a0c31559f74d2d84f858c
ERROR: error executing step command 'provision': deployment failed: failing invoking action 'provision', error deploying infrastructure: deploying to subscription:
Deployment Error Details:
VaultNameNotValid: The vault name 'codebreakercosmoskvzehizmlsmqemc' is invalid. A vault's name must be between 3-24 alphanumeric characters. The name must begin with a letter, end with a letter or digit, and not contain consecutive hyphens. Follow this link for more information: https://go.microsoft.com/fwlink/?linkid=2147742
The vault name is prefixed from the Azure Cosmos DB resource, this results in a vault name longer than 24 characters.
Expected behavior
I expect to have a key vault name generated that's valid or get a warning before deploying the other resources.
Environment
Information on your environment:
* Version 17.10.0 Preview 1.0
* aspire 8.0.0-preview.5.24156.15/8.0.100
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
christiannagel
changed the title
['Issue] Azure Key Vault name generated is too long when generated from an Azure Cosmos DB resource
[Issue] Azure Key Vault name generated is too long when generated from an Azure Cosmos DB resource
Mar 7, 2024
@vhvb1989 can you please reference the issue for the known bug, so I know when I can change the names back?
I'm currently using these versions with this issue:
aspire 8.0.0-preview.6.24177.4/8.0.100
azd version 1.7.0 (commit 49d6adc)
@christiannagel , I tried to find the issue on dotnet/aspire that is tracking the refactorization I mentioned, but I gave up. Maybe @davidfowl knows the issue better.
However, that change won't make it to Aspire p5, so, I'm opening this issue to fix this on azd until then.
Output from
azd version
Run
azd version
and copy and paste the output here:azd version 1.7.0-beta.1-pr.3518885 (commit d62cc4c)
Describe the bug
Using .NET Aspire, when using an Azure Cosmos DB resource, an Azure Key Vault that is generated, the vault's name is too long.
I had this deployment error running
azd up
:Using this app model:
This is the generated manifest:
The vault name is prefixed from the Azure Cosmos DB resource, this results in a vault name longer than 24 characters.
Expected behavior
I expect to have a key vault name generated that's valid or get a warning before deploying the other resources.
Environment
Information on your environment:
* Version 17.10.0 Preview 1.0
* aspire 8.0.0-preview.5.24156.15/8.0.100
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: