Back to Azure Resource templates index <–
Azure Database for PostgreSQL servers
Template Locations
Infrastructure As Code Advisor (Beta)
WAF-compliance
The WAF-compliance advisor validates templates based on the Well Architected Framework practices. Every day a GitHub Action updates the templates compliance data and lists the recomendations.
Sustainbility Advisor
The sustainability advisor is based on the Sogeti Cloud Reference Architecture with sustainble practices. These sustainble practices cover application code, cloud infrastructures and data. The global Sogeti community is continously evolving the sustainble practices and every day new and tuned are added. For cloud infrastructures the sustainble practices are automatically validated and reported below.
note: when 100% it can be that there is no sustainble practices yet for this Cloud infrastructure.
Online documentation
Template reference
Service description
Requirements
- Resource group must been created with a valid name and location.
Input values
- tagBillingIdentifier: Cost Center.
- adminUsername: Username of the administrator.
- adminPassword: Password of the administrator.
- VirtualCores: Virtual cores of the server.
- skuFamily: Compute generation of the server.
- skuSizeMB: Size of the database.
- skuTier: Pricing Tier of the server.
- version: Version of the PostgreSQL database.
- backupRetentionDays: Number of days database backup to be retained.
- geoRedundantBackup: Enabling this would enable Geo-Redundant replication for recovery from regional outage or disaster. Disabling this enable Locally-Redundant replication for recovery from data loss within region.
- firewallRuleName: Firewall Rule name.
- firewallStartIpAddress: Start IP of Firewall rule
- firewallEndIpAddress: End IP of Firewall rule
Output values
- serverName
Compliance Advisor details
Resource Health Result
| Message | ResourceType | Severity |
|---|---|---|
| Location for the resource should not be hardcoded, it should be parameterized and should refer from Resource Group's location i.e. [resourceGroup().location] | Microsoft.DBforPostgreSQL/servers | 2 |
| Your current API Version i.e.2017-12-01 for the resource Microsoft.DBforPostgreSQL/servers is outdatedconsider updating to new recent version available i.e. 2017-12-01-preview | Microsoft.DBforPostgreSQL/servers | 2 |
| To help other contributors understand the purpose of the resource, specify comments for each resource in the template | Microsoft.DBforPostgreSQL/servers | 1 |
| It is recommended to parameterized your tag and make it as object type | Microsoft.DBforPostgreSQL/servers | 1 |
TemplateParameterHealthResult
| Message | Severity |
|---|---|
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. tagBillingIdentifierRead More | 1 |
| It is recommended to make your parameter as camel case, wherever possible for i.e. servercustomnameRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. servercustomnameRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. adminUsernameRead More | 1 |
| It is recommended to make your parameter as camel case, wherever possible for i.e. VirtualCoresRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. VirtualCoresRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. skuTierRead More | 1 |
| It is recommended to make your parameter as camel case, wherever possible for i.e. versionRead More | 1 |
| It is recommended to add description for your parameters i.e. for firewallRuleNameRead More | 1 |
| It is recommended to add description for your parameters i.e. for firewallStartIpAddressRead More | 1 |
| It is recommended to add description for your parameters i.e. for firewallEndIpAddressRead More | 1 |
TemplateVariableHealthResult
| Message | Severity |
|---|---|
| It is recommended to make your variable as camel case, wherever possible for e.g. environmentRead More | 1 |
| It is recommended to make your variable as camel case, wherever possible for e.g. servernametrimRead More | 1 |
| It is recommended to make your variable as camel case, wherever possible for e.g. servernamedefaultRead More | 1 |
| It is recommended to make your variable as camel case, wherever possible for e.g. servernameRead More | 1 |
| It is recommended to make your variable as camel case, wherever possible for e.g. locationRead More | 1 |
| It is recommended to make your variable as camel case, wherever possible for e.g. skuRead More | 1 |