Welcome to python-kong’s documentation!

Contents:

Overview

python-kong

docs Documentation Status
tests
Travis-CI Build Status AppVeyor Build Status
Coverage Status Scrutinizer Status
package PyPI Package latest release PyPI Package monthly downloads

A Python client for the Kong API (http://getkong.org/)

  • Free software: BSD license

Installation

pip install python-kong

Development

To run the all tests run:

tox

Installation

At the command line:

pip install python-kong

Usage

To use python-kong in a project:

import kong

Reference

kong

Contributing

Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.

Bug reports

When reporting a bug please include:

  • Your operating system name and version.
  • Any details about your local setup that might be helpful in troubleshooting.
  • Detailed steps to reproduce the bug.

Documentation improvements

python-kong could always use more documentation, whether as part of the official python-kong docs, in docstrings, or even on the web in blog posts, articles, and such.

Feature requests and feedback

The best way to send feedback is to file an issue at https://github.com/vikingco/python-kong/issues.

If you are proposing a feature:

  • Explain in detail how it would work.
  • Keep the scope as narrow as possible, to make it easier to implement.
  • Remember that this is a volunteer-driven project, and that contributions are welcome :)

Development

To set up python-kong for local development:

  1. Fork python-kong on GitHub.

  2. Clone your fork locally:

    git clone git@github.com:your_name_here/python-kong.git
    
  3. Create a branch for local development:

    git checkout -b name-of-your-bugfix-or-feature
    

    Now you can make your changes locally.

  4. When you’re done making changes, run all the checks, doc builder and spell checker with tox one command:

    tox
    
  5. Commit your changes and push your branch to GitHub:

    git add .
    git commit -m "Your detailed description of your changes."
    git push origin name-of-your-bugfix-or-feature
    
  6. Submit a pull request through the GitHub website.

Pull Request Guidelines

If you need some code review or feedback while you’re developing the code just make the pull request.

For merging, you should:

  1. Include passing tests (run tox) [1].
  2. Update documentation when there’s new API, functionality etc.
  3. Add a note to CHANGELOG.rst about the changes.
  4. Add yourself to AUTHORS.rst.
[1]

If you don’t have all the necessary python versions available locally you can rely on Travis - it will run the tests for each change you add in the pull request.

It will be slower though ...

Tips

To run a subset of tests:

tox -e envname -- py.test -k test_myfeature

To run all the test environments in parallel (you need to pip install detox):

detox

Authors

Changelog

0.1.7 (2015-07-30)

  • Implemented APIAdminContract.add_or_update API
  • Implemented APIPluginConfigurationAdminContract.create_or_update API
  • Implemented ConsumerAdminContract.create_or_update API

0.1.6 (2015-07-28)

  • Updated KongAdminSimulator constructor to accept api_url

0.1.5 (2015-07-28)

  • Added CollectionMixin to contract (abstract base classes)

0.1.4 (2015-07-28)

  • Bugfix related to checking for API conflicts

0.1.3 (2015-07-28)

  • Added more tests and ‘CollectionMixin’ that exposes an ‘iterate’ api

0.1.2 (2015-07-27)

  • Implemented ‘plugin configuration’ update API

0.1.1 (2015-07-24)

  • Package structure updated

0.1.0 (2015-07-23)

  • First release on PyPI.

Indices and tables