-
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
[service_fabric] Don't pass the reverse proxy port if not set #2747
Conversation
Hi @hbuckle, Thanks for the PR. I'm not sure why In addition could we get a test for updating the port, something like empty -> 7777 -> empty ? |
@katbyte I've pushed the test and I'll look at adding the additional update one as well |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix @hbuckle, LGTM 👍
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 👉 hashibot-feedback@hashicorp.com. Thanks! |
This prevents the reverse proxy port being passed to the API when not specified. Previously if you didn't specify it then a value of
0
was passed, which breaks the cluster provisioning.I tried adding a test for this using
TestCheckNoResourceAttr
but I always getCheck failed: Check 6/12 error: azurerm_service_fabric_cluster.test: Attribute 'node_type.0.reverse_proxy_endpoint_port' found when not expected
so not sure if I am using it correctly?