Skip to content
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

Restructure config to support multiple instances of gateway with different configuration parameters #1

Merged
merged 7 commits into from
Jul 1, 2014

Conversation

kotrakrishna
Copy link
Contributor

No description provided.

…ows us to have two instances of same gateway but with different configuration.

- Omnipay services uses the 'omnipay.gateway_name.gateway' parameter to identify the Class name for the gateway.
 - Pass the gateway name to the service instead of gateway class to get an instance of gateway
@kotrakrishna kotrakrishna changed the title Restructure config to support multiple instances of gateway with different configuration Restructure config to support multiple instances of gateway with different configuration parameters Jun 30, 2014
transactionKey: myTransactionKey
omnipay.authorize_net_aim.apiLoginId: myLoginId
omnipay.authorize_net_aim.transactionKey: myTransactionKey
omnipay.authorize_net_aim.gateway: AuthorizeNet_AIM
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to document what this parameter structure means. It's not obvious to newcomers what this means.

anush added a commit that referenced this pull request Jul 1, 2014
Restructure config to support multiple instances of gateway with different configuration parameters
@anush anush merged commit 11d6fa7 into xola:master Jul 1, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants