[Breaking change]: WithAccessKeyAuthenticaton and WithPasswordAuthentication create a keyvault resource in the app model #2889
Labels
⛓️💥 breaking-change
Issues or PRs tracking breaking changes.
doc-idea
Indicates issues that are suggestions for new topics [org][type][category]
in-pr
Pri1
High priority, do before Pri2 and Pri3
📌 seQUESTered
Identifies that an issue has been imported into Quest.
Milestone
Description
Relevant change dotnet/aspire#8171
Resources no longer
Version
.NET Aspire 9.2
Previous behavior
Before azd would automatically create and manage bicep resources and these were invisible to the app model so they could not be managed or customized in C#.
New behavior
In 9.2 we changed calling
WithKeyAccessAuthenticaton
on CosmosDb and AzureRedis orWithPasswordAuthentication
would add an emptykeyVaultName
parameter as a known parameter in the bicep. Now we directly create the key vault resource (or allow you to pass in a reference to another AzureKeyVault resource where the secret will be stored). The key vault secret names for connection strings are now namedconnectionstrings--{resourcename}
to avoid potential conflicts with other connection strings in existing key vaults.Type of breaking change
Reason for change
Moving resources to the app host makes it easier to customize and manage. You can now share a key vault across multiple resources or use an existing key vault to manage connection strings with secrets.
Recommended action
There is currently not work around.
Affected APIs
Associated WorkItem - 416256
The text was updated successfully, but these errors were encountered: