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
Having cybs.ini inside the sdk itself is great for tests and built-in samples but you really want to have the configuration within your application. In addition if you use something like Azure/heroku auto-deploys you really can't change anything in the SDK/vendor dirs.
What I was able to do to work around was just set the include path to the current dir, where my config was and maybe that's enough if it is documented.
set_include_path(getcwd());
The text was updated successfully, but these errors were encountered:
I would say the better workaround is to write a class that extends CybsClient and then write your own constructor. This also allows you to have more than one CyberSource account if need be.
I would say the better workaround is to write a class that extends CybsClient and then write your own constructor. This also allows you to have more than one CyberSource account if need be.
I agree with @thwiv, the package sould support manage more than one business account
Having cybs.ini inside the sdk itself is great for tests and built-in samples but you really want to have the configuration within your application. In addition if you use something like Azure/heroku auto-deploys you really can't change anything in the SDK/vendor dirs.
What I was able to do to work around was just set the include path to the current dir, where my config was and maybe that's enough if it is documented.
set_include_path(getcwd());
The text was updated successfully, but these errors were encountered: