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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for creating multiple private endpoints simultaneously #26005

Open
1 task done
lonegunmanb opened this issue May 17, 2024 · 0 comments 路 May be fixed by #26006
Open
1 task done

Support for creating multiple private endpoints simultaneously #26005

lonegunmanb opened this issue May 17, 2024 · 0 comments 路 May be fixed by #26006

Comments

@lonegunmanb
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

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 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants