You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 and review the contribution guide to help.
Description
In pr 16315 I've introduced an internal lock to enforce a serialized creation for private endpoints in one subnet, this behavior is caused by this API issue.
Some customers are complaining slow creation for hundreds of private endpoints, and after a test, we've verified that now we can create multiple private endpoints by using Bicep.
The API issue seems no longer exist, so we'd like to open a new pr to remove the internal serialize lock on subnet while processing private endpoint.
New or Affected Resource(s)/Data Source(s)
azurerm_private_endpoint
Potential Terraform Configuration
No response
References
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Community Note
Description
In pr 16315 I've introduced an internal lock to enforce a serialized creation for private endpoints in one subnet, this behavior is caused by this API issue.
Some customers are complaining slow creation for hundreds of private endpoints, and after a test, we've verified that now we can create multiple private endpoints by using Bicep.
The API issue seems no longer exist, so we'd like to open a new pr to remove the internal serialize lock on subnet while processing private endpoint.
New or Affected Resource(s)/Data Source(s)
azurerm_private_endpoint
Potential Terraform Configuration
No response
References
No response
The text was updated successfully, but these errors were encountered: