-
-
Notifications
You must be signed in to change notification settings - Fork 271
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
Regardless of Config, All Calls Go to Wrong DataCenter #434
Comments
@imageaid Good place for questions like this is the slack channel, Mike tries to keep issues to just issues and not questions unless that leads to a bug/issue, and then an issue can be created of course. Join the slack channel by going here: http://opensuite-slackin.herokuapp.com/ But, to possibly answer your question, there is something funky with the |
Ah crap! I totally spaced on adding a comment yesterday. I think you’re spot on with the sandbox resetting other configs. When I moved the `wsdl_domain` method below the other calls, making it the last one in the block, it held the value perfectly and all requests went to the right URL.
I forked the repo so I could explore the internals as I worked through this. Going to see if I can uncover where that’s happening and, if I can, I’ll submit a PR for review, etc.
Thanks for getting back to me and thanks to the team for all the work on this gem. It really makes the hell that is working with NetSuite a little better :). Appreciate it (and the heads up on the slack channel, too!!).
|
Yep, it's easy to locate the problem sandbox bit. I think I was going to possibly submit a PR as well, but I think it might be a good idea to just nix the sandbox altogether -- the logic included with that flag is older and tied to the sandbox domain. So that was before NS got rid of the sandbox domain. Which was before they've now gone to account specific URLs for both prod 12345.app/suitetalk/etc... and for sandbox too 12345-sb1.app/suitetalk/etc. So should probably look at removing sandbox, and making the |
I do like the idea of making wsdl_domain required given NetSuite's removal of their internal router and new requirement for accounts to use those specific, account-based Data Center URLs. |
Related to #430 |
#473 Fixed this issue. Closing this out. |
I am attempting to update our NetSuite gem's configuration so that our requests go to the "right" data center.
However, regardless of what I enter into the initializer, all requests go to the wrong data center, using the 'generic' wsdl:
https://webservices.netsuite.com/services/NetSuitePort_2017_2
as it appears to drop thena2.
from the 'correct' URL (see below).In my configuration/initializer, I have specified one of two options:
The long and short is that no matter what I have in the initializer/config file, the library only makes requests to "https://webservices.netsuite.com/services/NetSuitePort_2017_2". I have even tried as
wsdl "http://dumburls.com/i/hate/netsuite"
as a WSDL URL and it still just goes to the URL noted above.One final note: if I change the API Version in the config file, it DOES change the request to
https://webservices.netsuite.com/services/NetSuitePort_2015_1
but still ignores whatever I have forwsdl
orwsdl_domain
.Any direction or suggestions would be most appreciated and thank you!
The text was updated successfully, but these errors were encountered: