Azure / Azure/Azure-Landing-Zones
Private Link missing policy for some resources.
- Dominant language
- PowerShell
- Stars
- 96
- Forks
- 70
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 7
Description
### Community Note
- Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
### Description
#### Is your feature request related to a problem?
We are trying to exclusively use the policy provided to automatically associate all Private Endpoints to our centralised Private DNS Zones without having to give permissions to our workload Landing Zones. Assumingly there is a few more missing than we have noticed, but we are starting to collate a list of resources that we have noticed as missing:
#### Describe the solution you'd like
- Add support for Postgres - `privatelink.postgres.database.azure.com`
#### Additional context
Contributor guide
Research direction
Inspect the repository for the Private Link policy definitions and existing resource entries, then compare how PostgreSQL private endpoints are represented. Add the missing PostgreSQL resource using the existing policy structure and verify that the policy includes privatelink.postgres.database.azure.com.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, postgresql, powershell
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100