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
Description
The current implementation of azurerm_batch_pool contains a network_configuration block that only supports 'subnet_id' and 'endpoint_configuration'. The actual Batch Pool resource in Microsoft Azure (see https://docs.microsoft.com/en-us/azure/templates/microsoft.batch/2019-08-01/batchaccounts/pools) also includes a 'PublicIPs' field. Without this field, it is not always possible to set up the batch pool correctly (e.g. the nodes in the pool cannot be started or time out).
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!
ghost
locked and limited conversation to collaborators
Apr 4, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Description
The current implementation of
azurerm_batch_pool
contains anetwork_configuration
block that only supports'subnet_id'
and'endpoint_configuration'
. The actual Batch Pool resource in Microsoft Azure (see https://docs.microsoft.com/en-us/azure/templates/microsoft.batch/2019-08-01/batchaccounts/pools) also includes a 'PublicIPs' field. Without this field, it is not always possible to set up the batch pool correctly (e.g. the nodes in the pool cannot be started or time out).New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: