Fix Azure PostgreSQL AsExisting - #7699
#7699Merged
eerhardt merged 1 commit intoFeb 20, 2025
microsoft:mainmicrosoft/aspire:mainfrom
eerhardt:FixExistingAzurePostgreseerhardt/aspire:FixExistingAzurePostgresCopy head branch name to clipboard
Merged
Fix Azure PostgreSQL AsExisting#7699eerhardt merged 1 commit intomicrosoft:mainmicrosoft/aspire:mainfrom eerhardt:FixExistingAzurePostgreseerhardt/aspire:FixExistingAzurePostgresCopy head branch name to clipboard
eerhardt merged 1 commit into
microsoft:mainmicrosoft/aspire:mainfrom
eerhardt:FixExistingAzurePostgreseerhardt/aspire:FixExistingAzurePostgresCopy head branch name to clipboard
Conversation
In bicep, it is not supported to set properties on "existing" resources. When using AsExisting on an Azure PostgreSQL resource, we are setting authConfig properties to enable/disable password and activeDirectory auth. This is causing errors when trying to deploy because the bicep is invalid. Fix this by not setting these properties on existing resources. Instead for activeDirectory/Entra ID auth, we will add the principle as an admin on the server. For password auth on an existing resource, we expect the user to pass the correct username/password parameters to connect to the database server. Fix microsoft#7694
eerhardt
requested review from
captainsafia,
Copilot,
mitchdenny and
sebastienros
February 20, 2025 00:06
captainsafia
approved these changes
Feb 20, 2025
Member
Author
|
/backport to release/9.1 |
Contributor
|
Started backporting to release/9.1: https://github.com/dotnet/aspire/actions/runs/13426042503 |
mitchdenny
reviewed
Feb 20, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
In bicep, it is not supported to set properties on "existing" resources. When using AsExisting on an Azure PostgreSQL resource, we are setting authConfig properties to enable/disable password and activeDirectory auth. This is causing errors when trying to deploy because the bicep is invalid.
Fix this by not setting these properties on existing resources. Instead for activeDirectory/Entra ID auth, we will add the principle as an admin on the server. For password auth on an existing resource, we expect the user to pass the correct username/password parameters to connect to the database server.
Fix #7694
Checklist