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
Omitted, but I have a trace log of the bug and a working version - if needed.
Panic Output
No panic.
Expected Behavior
Expect a new Azure API Management API to be created with SOAP pass-through.
The property soap_pass_through is set to true in the state file, but that does not mean that the end-result is correct.
The correct property is not sent to the Azure REST API when the WSDL is sent in (during the import phase), meaning that the generated API operations are the same as having soap_pass_through=false.
Actual Behavior
The API operations are not created as expected with soap_pass_through=true. If you try to create a API in API Management and choose "Import WSDL" and "SOAP pass-through", none of the operations will not have any policies.
Instead, all endpoints are generated with policies that transform from JSON to XML and vice verca - the behavior that is expected if you do not choose SOAP pass-through.
Steps to Reproduce
Use the configuration above and create a API in an existing API Management instance.
Important Factoids
I have found the bug and fixed it. I have verified it by building my own version of the provider and testing it.
PR is coming.
References
None. I will submit a PR later.
The text was updated successfully, but these errors were encountered:
I am not completely sure if the modified block (line 222-229) is 100 % correct.
Not sure if there can be other combinations of those properties.
The change has been tested and verified locally for both soap_pass_through = true and false
Fixeshashicorp#5080
Details in PR
I am not completely sure if the modified block (line 222-229) is 100 % correct.
Not sure if there can be other combinations of those properties.
The change has been tested and verified locally for both soap_pass_through = true and false
Fixes#5080
Details in PR
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!
ghost
locked and limited conversation to collaborators
Mar 29, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform (and AzureRM Provider) Version
Terraform v0.12.16
azurerm v1.37.0 (and older)
Affected Resource(s)
azurerm_api_management_api
Terraform Configuration Files
Debug Output
Omitted, but I have a trace log of the bug and a working version - if needed.
Panic Output
No panic.
Expected Behavior
Expect a new Azure API Management API to be created with SOAP pass-through.
The property
soap_pass_through
is set totrue
in the state file, but that does not mean that the end-result is correct.The correct property is not sent to the Azure REST API when the WSDL is sent in (during the import phase), meaning that the generated API operations are the same as having
soap_pass_through=false
.Actual Behavior
The API operations are not created as expected with
soap_pass_through=true
. If you try to create a API in API Management and choose "Import WSDL" and "SOAP pass-through", none of the operations will not have any policies.Instead, all endpoints are generated with policies that transform from JSON to XML and vice verca - the behavior that is expected if you do not choose SOAP pass-through.
Steps to Reproduce
Use the configuration above and create a API in an existing API Management instance.
Important Factoids
I have found the bug and fixed it. I have verified it by building my own version of the provider and testing it.
PR is coming.
References
None. I will submit a PR later.
The text was updated successfully, but these errors were encountered: