-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port allocation does not set to use the default number of outbound ports #16343
Comments
Hi @tanvp112 this seems to be a bug in the provider that |
I look forward to the fix in the provider soon, thanks for the prompt replied. |
Fix #16343 0 seems to be a valid input for allocated_outbound_ports, adding validation and use d.Get instead of d.GetOk to include it. Adding the missing default value of 1024 in doc There seems to be not test around allocated_outbound_ports, adding it as well.
This functionality has been released in v3.2.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Is there an existing issue for this?
Community Note
Terraform Version
1.1.8
AzureRM Provider Version
3.1.0
Affected Resource(s)/Data Source(s)
azurerm_lb_outbound_rule
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
An outbound rules of port allocation set to zero with Port allocation set to "Use the default number of outbound ports" should be created.
Actual Behaviour
An outbound rule of port allocation is set to 1024 despite
allocated_outbound_ports = 0
was specified in the code, and Port allocation required manual intervention to set it to "Use the default number of outbound ports".Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: