Skip to content

Aspire 9.2 - ACA *Possible Breaking Change* #8695

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
maddymontaquila opened this issue Apr 10, 2025 · 0 comments
Open

Aspire 9.2 - ACA *Possible Breaking Change* #8695

maddymontaquila opened this issue Apr 10, 2025 · 0 comments
Labels
area-azure-aca area-deployment area-meta azure Issues associated specifically with scenarios tied to using Azure

Comments

@maddymontaquila
Copy link
Member

Hi folks! Aspire 9.2 ships April 10 and there is one breaking change for anyone deploying Azure SQL Server or Azure PostgreSQL to ACA.

We now support multiple managed identities for your database containers, meaning you will have to either give permission to an existing managed identity or create a new one to do your database operations.

You can find more details and the workaround in the docs issue.

We don't like breaking things on minor versions, but this is both a highly-requested feature and an important step towards more secure defaults. You can track issue #8389 where we're working on a mitigation.

@maddymontaquila maddymontaquila pinned this issue Apr 10, 2025
@maddymontaquila maddymontaquila changed the title Aspire 9.2 - ACA **Breaking Change** Aspire 9.2 - ACA *Possible Breaking Change* Apr 10, 2025
@maddymontaquila maddymontaquila added azure Issues associated specifically with scenarios tied to using Azure area-azure-aca area-deployment labels Apr 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-azure-aca area-deployment area-meta azure Issues associated specifically with scenarios tied to using Azure
Projects
None yet
Development

No branches or pull requests

1 participant