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

Azure Synapse Analytics - createManagedPrivateEndpoint feature not idempotent #17346

Open
dpmcclurg opened this issue Jan 13, 2022 · 0 comments
Open

Azure Synapse Analytics - createManagedPrivateEndpoint feature not idempotent #17346

dpmcclurg opened this issue Jan 13, 2022 · 0 comments
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. 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. Synapses

Comments

@dpmcclurg
Copy link

dpmcclurg commented Jan 13, 2022 •
edited
Loading

As @dubansal mentions in #15602, creating a managed private endpoint on the default storage account of a Synapse workspace is designed only to be executed when first creating the workspace. Without wrapping this property in conditional logic, any repeated use of this API through, say, Azure Bicep will fail, even if the property remains unchanged in subsequent deployments.

A fix for this appears to be the x-ms-mutability extension. Currently, the createManagedPrivateEndPoint feature is set to Create and Update. Would setting it to Create and Read be more appropriate?

Screenshot 2022-01-13 171812
@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. 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 Jan 13, 2022
@ankhyk ankhyk added Service Attention Workflow: This issue is responsible by Azure service team. Synapses labels Jan 14, 2022
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jan 14, 2022
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. 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. Synapses
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ankhyk @dpmcclurg