Closed christiannagel closed 7 months ago
@vhvb1989 @davidfowl don't think its a blocker for Preview 4 release. Adding it to Preview 5.
Closing as a known bug for preview4 and as a feature to be changed for preview5.
@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 49d6adc2efb178083f61822e6b4715258560803d)
@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.
Thank you for bringing this up
Output from
azd version
Runazd version
and copy and paste the output here: azd version 1.7.0-beta.1-pr.3518885 (commit d62cc4c16bda2eefabf48b7d7f8bd616cad1445a)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:
Additional context Add any other context about the problem here.