Spike Arrest policy fails schema validation

simonvergara · 03-01-2018 12:04 PM

Im using the Spike Arrest policy to limit the tpm of my API. I want to use the UseEffectiveCount element that Apigee has. It seems to work fine and it saves perfectly fine.

However, when I try to promote my changes to a different environment of Apigee (by downloading the .zip from the source environment and uploading it to the destination environment) the process fails and I get an error saying that it doesn't pass schema validation.

Am I doing something wrong?

Error:

My Policy:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<SpikeArrest async="false" continueOnError="false" enabled="true" name="Dynamic-Spike">
    <DisplayName>Dynamic Spike</DisplayName>
    <Properties/>
    <Identifier ref="client_id"/>
    <Rate ref="verifyapikey.Verify-API-Key.developer.allowed_spike">50pm</Rate>
    <UseEffectiveCount>true</UseEffectiveCount>
</SpikeArrest>

DChiesa

You're not doing anything wrong.

That feature was added in Apigee Edge SaaS 180202. See the release notes.

So it seems your "different environment" is not yet updated to 180202.

I don't know why that would be. You can ask Apigee Support, if you have a support contract.

simonvergara

I forgot to mention that I'm using on prem. And the target environment (4.17.09) is actually ahead of the source environment (4.17.05).

Thanks, I'll get in contact with support. I just wanted to check I wasn't missing something obvious.