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.

Sign up for GitHub

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

Jump to bottom

PostgreSQL Flexible Server - Private DNS Zone ID returns inconsistent casing #26346

Open
mbfrahry opened this issue Oct 23, 2023 · 0 comments
Open

PostgreSQL Flexible Server - Private DNS Zone ID returns inconsistent casing #26346

mbfrahry opened this issue Oct 23, 2023 · 0 comments
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. PostgreSQL question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@mbfrahry
Copy link
Contributor

The casing for PostgreSQL Flexible Server is inconsistent when it comes to the Private DNS Zone ID.

Private DNS Zone ID returns the correct casing when it is managed solely through the api. But when it is updated through the portal, the casing is returned by the api as all lower case.

Similar to #6641
@microsoft-github-policy-service microsoft-github-policy-service bot added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Oct 23, 2023
@JackTn JackTn added PostgreSQL Service Attention Workflow: This issue is responsible by Azure service team. and removed CXP Attention labels Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. PostgreSQL question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mbfrahry @JackTn