-
Notifications
You must be signed in to change notification settings - Fork 701
Closed
Labels
area-integrationsIssues pertaining to Aspire Integrations packagesIssues pertaining to Aspire Integrations packagesazureIssues associated specifically with scenarios tied to using AzureIssues associated specifically with scenarios tied to using AzurepostgresIssues related to Postgres integrationsIssues related to Postgres integrations
Milestone
Description
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
When using AddAzurePostgresFlexibleServer and AsExisting, the bicep we generate doesn't work. You get an error on startup:
pg.module.bicep(12,3) : Error BCP173: The property "properties" cannot be used in an existing resource declaration. [https://aka.ms/bicep/core-diagnostics#BCP173]
Expected Behavior
I expect to use an existing Azure PostgreSQL server in my app.
Steps To Reproduce
var serverName = "myserver";
var rg = "myresourcegroup";
var db = builder.AddAzurePostgresFlexibleServer("pg")
.RunAsExisting(serverName , rg)
.AddDatabase("db");
When you F5 you get the above error when it tries provisioning.
Exceptions (if any)
No response
.NET Version info
No response
Anything else?
Metadata
Metadata
Assignees
Labels
area-integrationsIssues pertaining to Aspire Integrations packagesIssues pertaining to Aspire Integrations packagesazureIssues associated specifically with scenarios tied to using AzureIssues associated specifically with scenarios tied to using AzurepostgresIssues related to Postgres integrationsIssues related to Postgres integrations