3scale-qe/3scale-api-python

3scale API Python Client

3scale-api-python's Issues

[TEST] Integration tests: method, metric, mapping rules

CRUD Tests for:

• method
• metric
• mapping rules

change creating dictionaries

change dict() to plane dictionary {} when there is a need to create dictionary with params

Billing and pricing rules

Features:

• Billing
• Pricing rules

Policies.append() should accept list

Policies.append (and even Polciies.insert) should support list [policy] as argument to append all in one call (avoid multple calls of .append() as each .append() means 2 remote calls)

map_new_metric method might be handy

it seems to be common to create some metric and create mapping rule to that new metric
that requires 3 calls: metrics.create, mapping_rules.create, proxy.update

having method call to do it all in one step (metric and mapping definitions as args) can be useful

no LICENSE file?

Repo is missing a LICENSE file. We are evaluating using this library as part of a paid commercial training. We would like to understand the licensing terms

Where i can find docs?

Hey! thanks for building this kind of library.
I want to start using this library but I cant find any docs. Can you share some knowledge?

For example, its confusing how to get an application plan, how do I access the data?
there are few options : threescale_api.client.resources.ApplicationPlan / get / fetch' / read`.

page client

transfer CMS client paging part to Pageclient