Difference between revisions of "Poppy/Provider - Getting Started/Configuration"
Amit Gandhi (talk | contribs) |
Amit Gandhi (talk | contribs) (→Configuring your Driver) |
||
Line 18: | Line 18: | ||
== Configuring your Driver == | == Configuring your Driver == | ||
/etc/poppy.conf:: | /etc/poppy.conf:: | ||
+ | |||
+ | Add your provider as a valid option for Poppy to use:: | ||
# Provider modules list (a list of comma separated provider module list) | # Provider modules list (a list of comma separated provider module list) | ||
providers = mock,fastly,akamai,{your_provider_name} | providers = mock,fastly,akamai,{your_provider_name} | ||
+ | Set up any provider specific configuration parameters that the operator can set:: | ||
[drivers:provider:{your_provider_name}] | [drivers:provider:{your_provider_name}] | ||
Line 27: | Line 30: | ||
apikey = "MY_APIKEY" | apikey = "MY_APIKEY" | ||
− | where username and apikey | + | where username and apikey could be configuration parameters that your driver requires to communicate with your backend api. |
Revision as of 21:59, 26 January 2015
Congratulations! If you made it here, then you must have a provider ready to go =)
Poppy uses the Stevedore framework to configure Drivers into the application.
Register your provider in Stevedore
/setup.cfg::
Add an entry point in setup.cfg so that Poppy recognizes your new driver and operators can start to use it.
poppy.provider = {your_provider_name} = poppy.provider.{your_provider_name}:Driver
This will allow Poppy to detect your provider, and use it in configurations.
Once you have registered your Stevedore plugin, please add it to the configuration.
Configuring your Driver
/etc/poppy.conf::
Add your provider as a valid option for Poppy to use::
# Provider modules list (a list of comma separated provider module list) providers = mock,fastly,akamai,{your_provider_name}
Set up any provider specific configuration parameters that the operator can set::
[drivers:provider:{your_provider_name}] username = "MY_USERNAME" apikey = "MY_APIKEY"
where username and apikey could be configuration parameters that your driver requires to communicate with your backend api.