Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request - Private Link missing policy for some resources. #1142

Open
ryan-royals opened this issue Sep 30, 2024 · 0 comments
Open

Feature Request - Private Link missing policy for some resources. #1142

ryan-royals opened this issue Sep 30, 2024 · 0 comments

Comments

@ryan-royals
Copy link
Contributor

ryan-royals commented Sep 30, 2024

Community Note

  • Please vote on this issue by adding a 👍 reaction 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

@ryan-royals ryan-royals changed the title Feature Request - PDNS missing policy for some resources. Feature Request - Private Link missing policy for some resources. Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant