Azure / Azure/azure-rest-api-specs
Postgresql securityAlertPolicies returns empty string
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
Related to https://github.com/terraform-providers/terraform-provider-azurerm/issues/8738
PUT /subscriptions/.../resourceGroups/.../providers/Microsoft.DBforPostgreSQL/servers/.../securityAlertPolicies/Default?api-version=2017-12-01 HTTP/1.1
{"properties":{"state":"Enabled","disabledAlerts":[],"emailAddresses":[],"emailAccountAdmins":false,"retentionDays":0}}
GET /subscriptions/.../resourceGroups/.../providers/Microsoft.DBforPostgreSQL/servers/.../securityAlertPolicies/Default?api-version=2017-12-01 HTTP/1.1
{"properties":{"state":"Enabled","disabledAlerts":[""],"emailAddresses":[""],"emailAccountAdmins":false,"storageEndpoint":"","storageAccountAccessKey":"","retentionDays":0,"creationTime":"2020-10-13T07:51:56.52Z"},"id":"...","name":"Default","type":"Microsoft.DBforPostgreSQL/servers/securityAlertPolicies"}
Contributor guide
Research direction
Start by reviewing the PostgreSQL securityAlertPolicies definition in the Azure REST API specifications and compare the PUT and GET examples in this issue and the related issue 8738. Determine how the specification should represent the empty disabledAlerts, emailAddresses, and storage fields, then verify that the corrected definition matches the service responses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, openapi, postgresql
- Domain
- api, cloud, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100