Skip to content

Commit 1fbd9df

Browse files
Fix blog 5.4: correct plan name to asp-talent-f1-dev, note system master database
1 parent bf809e2 commit 1fbd9df

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

blogs/series-5-devops-data/5.4-azure-bicep-infrastructure.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -280,7 +280,7 @@ resource apiDatabase 'Microsoft.Sql/servers/databases@2023-05-01-preview' = {
280280
281281
using '../main.bicep'
282282
283-
param appServicePlanName = 'asp-talent-b1-dev'
283+
param appServicePlanName = 'asp-talent-f1-dev'
284284
param apiAppName = 'app-talent-api-dev'
285285
param identityAppName = 'app-talent-ids-dev'
286286
param identityAdminAppName = 'app-talent-admin-dev'
@@ -352,7 +352,7 @@ az resource list \
352352
--output table
353353
```
354354

355-
You should see eight resources: one App Service Plan, three Web Apps, one Static Site, one SQL Server, and two SQL Databases.
355+
You should see eight resources: one App Service Plan, three Web Apps, one Static Site, one SQL Server, and two SQL Databases. Azure also lists a `master` database — this is a system database automatically created by Azure SQL and does not count as one of your provisioned resources.
356356

357357
Navigate to each Web App in the Portal (`portal.azure.com → App Services → app-talent-api-dev`) and confirm the URL opens — it will show a default "Your web app is running" page until the .NET application is deployed in Article 5.6.
358358

0 commit comments

Comments
 (0)