Partitioned policy when field not set in key

Support
, ,
7

Sorry to say it didn’t answer it. I doubt if you are not still getting to my point.

Key

{
    "expires": -1,
    "quota_max": 50,
    "quota_renewal_rate": 60,
    "org_id": "basic",
    "access_rights": {
        "test-api-id": {
            "api_name": "Test api",
            "api_id": "test-api-id",
            "versions": ["Default"]
        }
    },
    "meta_data": {},
    "basic_auth_data": {
        "password": "test-password"
    },
    "hmac_enabled": false,
    "hmac_string": "",
    "is_inactive": false,
    "apply_policy_id": "",
    "apply_policies": ["partitioned"],
    "monitor": {
        "trigger_limits": []
    }
}

Policy

"partitioned": {
        "rate": 12,
        "per": 1,
        "quota_max": 24,
        "quota_renewal_rate": 60,
        "access_rights": {
            "test-api-id": {
                "apiname": "Test api",
                "apiid": "test-api-id",
                "versions": ["Default"]
            }
        },
        "org_id": "basic",
        "hmac_enabled": false,
        "partitions": {
            "quota": true,
            "rate_limit": false,
            "acl": true,
            "complexity": true
        }
    }

Here, notice rate limit of policy “partitioned” is being partitioned but there isn’t any “rate” or “per” fields defined in key. In this case I want to use rate of 12 request per second which is defined in the policy “partitioned” to be used instead. When I try it out it does not keep any rate limit and passes as many requests per second without any restrictions.